Settings and activity
39 results found
-
1 vote
An error occurred while saving the comment -
366 votes
An error occurred while saving the comment We have had to pause development of this feature while we focus on finishing work on spaces. We expect to get back to complete this work sometime in the next quarter.
An error occurred while saving the comment @ChrisCamburn we are looking at adding support to expose package selection on step templates out to the consuming project so that users no longer need to rely on variables to get different package values into a step template.
https://github.com/OctopusDeploy/Issues/issues/4270
Would this solve your problem? -
4 votes
An error occurred while saving the comment We currently expose the sha256 hash through the HTTP header through the MSI download link.
The header is `x-amz-meta-sha256` alongside the existing `x-amx-meta-md5`. Although this is not immediately provided through the portal this will provide the required information.e.g for
https://download.octopusdeploy.com/octopus/Octopus.2018.6.2-x64.msi
the HTTP headersx-amz-meta-sha256: B371FB0775867E1CBE29DA977F4FDCABBA6E58855EBEF15D13FB2998AF520B3C
and
x-amz-meta-md5: 7C44113ABB87335356937247862CEC7Dare both provided
-
4 votes
An error occurred while saving the comment We have added some new features in the 2018.5 release for dynamic Azure targets that may support this.
Please see the following pages for more information:
- https://octopus.com/blog/paas-targets
- https://octopus.com/blog/octopus-release-2018.5
- https://octopus.com/docs/infrastructure/dynamic-infrastructure -
7 votes
An error occurred while saving the comment The task list currently (as of 4.0) provides the ability to view all running tasks. Does this feature meet your requirements?
-
5 votes
An error occurred while saving the comment Hi @Grendizr
Octostache, the templating library that is used, is fully open source so we are happy to receive pull requests
https://github.com/OctopusDeploy/Octostache -
18 votes
AdminProduct Team
(Admin, Octopus Deploy)
shared this idea
·
-
1 vote
An error occurred while saving the comment Is there any reason you are unable to use the existing subscriptions feature to handle this scenario? (https://octopus.com/docs/administration/subscriptions)
see related ticket https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/18629887-provide-a-way-to-send-notifications-from-failed-ta
-
1 vote
An error occurred while saving the comment @Scott are you aware that you can already configure your dashboard to only show specific projects and environments?
-
0 votes
An error occurred while saving the comment Geert, Project variables can already be scoped to steps.
https://octopus.com/docs/deployment-process/variables/scoping-variables#Scopingvariables-Scopespecificity
Is this something not working for you? -
14 votes
An error occurred while saving the comment Is there a concern or problem using SQL Server? Supporting other RDBMS would add a load of additional development, maintenance and support overheads so would be an unlikely option unless there are important issues. If it is a problem with installing and managing this peice of infrastructure is it possible to just use Microsoft Azure SQL Database or AWS RDS SQL Database?
https://octopus.com/docs/installation/sql-server-database-requirements#SQLServerDatabaseRequirements-Supportedversionsandeditions -
14 votes
An error occurred while saving the comment Our recommended approach for this is to have a single transform file in your solution, for example web.octopus.config, which contains placeholders for octopus variables, e.g. #{ConnectionString}.
During deployment, you run variable-substitution on that transform file, and then use it to perform the transform.
This achieves the goals of:
- Storing variables in Octopus
- Your solution doesn't have to know about environments
- But knowledge of the actual structure of the config file is all contained in your solution. -
39 votes
An error occurred while saving the comment @Thomas
Could you expand on the use-case. I assume you would not be using variable substitution, scripts or config transforms on the files in that folder? Do you use Custom Installation directories?
A small correction, the path is extracted to `C:\Octopus\Applications\tenant1\Production\packageName\v_0.0.1` (ie packageName instead of projectName).
Once the files are extracted we use that folder to run the scripts for the other features (eg IIS configuration, config transform, pre/post scripts).
Could you use the transfer package step and then a script step to conditionally unpack the package? You could also have a script step at the start that figures out if you have to do anything, then sets an output variable that is used to conditionally run the next two steps.
-
4 votes
An error occurred while saving the comment A step with similar functionality exists in the Octopus community library
https://library.octopus.com/step-templates/c8781255-615a-4092-99f1-82ddefdb6d6b/actiontemplate-wait-until-time -
2 votes
An error occurred while saving the comment Is there any reason that our existing proxy support does not meet these needs?
https://octopus.com/docs/infrastructure/windows-targets/proxy-support -
21 votes
An error occurred while saving the comment It is hard to decide how such a feature would be able to be natively implemented. The best suggestion would be for users to bundle an uninstall.ps1 script (to ensure that the uninstall process is tied to the version deployed) then use the Octopus.Tentacle.Package.PreviousInstallDirectory variable in a script before the "new" deployment step to access and invoke that script on subsequent deployments.
How would Octopus be expected to uninstall if for example roles are removed from a machine? We then no longer have any way of knowing what machines were involved in that release or if it should be our responsibility to now try and connect to something that has explicitly been changed to no longer be part of that deployment.
-
23 votes
An error occurred while saving the comment This is available from the community library
https://library.octopus.com/step-templates/58399364-4367-41d5-ad35-c2c6a8258536/actiontemplate-sql-deploy-dacpac -
1 vote
An error occurred while saving the comment Maven repositories like Nexus are now supported in 4.1. See http://g.octopushq.com/OnboardingFeedsMavenLearnMore for more details.
-
8 votes
An error occurred while saving the comment Is there any reason the package can't just be pushed to the NuGet feed initially rather than Octopus Deploy's built-in feed?
-
2 votes
An error occurred while saving the comment @Mehmet does the existing features described in https://octopus.com/docs/deploying-applications/substitute-variables-in-files or https://octopus.com/docs/deploying-applications/configuration-files not already cover whatr you are after?
Hey Jose, does the Package Requirement condition ( https://octopus.com/docs/deployment-process/conditions#package-requirement ) not allow you to achieve this?