522 results found
-
Deploy a release - accessing variables from last release
As per - https://help.octopus.com/t/deploy-a-release-accessing-variables-from-last-release/22788
You should be able to access a previous releases Step output variables, for when a release has already been deployed.
Either via the Deploy a release step.
Or more generally to retrieve these values for a given release.
E.g. an obtain Release information step1 vote -
"Deploy a release step" allow choosing target environment
The deploy release step assumes want to deploy to the same environment as the parent deployment.
Add facility to pass a parameter to chose which environment to deploy the release too.
E.g. so can deploy a single master release, which kicks off multiple deployments of other release to the defined environments specified by the parameters.Similar to how the community Chain step template allows for.
1 vote -
Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects
Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects
18 votes -
Pre-caching / Pre-acquiring of packages for scheduled deployments
We deploy our packages to our customer environments.
For example 1.5GB of packages to 500 targets over the internet. As the internet connections can be slow and to make sure that the deployments all take place at the same (scheduled) time I suggest that the "acquiring packages" step optionally starts as soon as a deployment is scheduled and verified again at the scheduled execution time. Should the deployment package(s) be missing or corrupt at the scheduled execution time there could also be an option "re-aquire at execution"/"fail if missing".1 vote -
See references to projects used in 'Deploy a Release' steps
In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.
Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.
3 votes -
Add a view that shows all Releases across all channels and Tenants
Please can a view be added that allows a user to see all deployments in a pipeline, spanning all tenants and channels? Having to search for these seperately causes no end of headaches as I often have to line up versions and this is made harder when they have to be searched for. Making it so they are all visible from the main page of a release as an optional view would alleviate this.
1 vote -
"Acquire Packages" should be first step
Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.
Our use case:
We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.Our current fix:
Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning1 vote -
Allow MarkDown files from a package to be used as manual intervention
Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.
I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.
However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the deployment.
2 votes -
Improve "Substitute Variables in Files" help text for "Run a Script"
When you configure a "Run a Script" deployment step, you can reference a package, and add the "Substitute Variables in Files" feature. Within the help text it says "A newline-separated list of file names to transform, relative to the package contents." which is inaccurate:
For me, using a simple, relative path here e.g. "index.html" didn't work. I needed to use the full extracted path of the package e.g:
{Octopus.Action.Package[EdibleCode.Something].ExtractedPath}\index.html
Also, you can reference multiple packages for a a run a script template, in which case "relative to the package contents" doesn't make sense and needs clarifying.
1 vote -
Sort pipe for #each iterations
When iterating through a collection variable using #{each var in array}, it would be helpful to have a sort by pipe
Eg: #{each var in array | orderby var.property}1 vote -
Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button
Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button. This is the same thing that Octopus already has for variables. Just do it for Processes!
Nothing worse than having to make a small powershell script change then create a new release and run it back up the runway or having to temporarily manipulate the lifecycle to get it re-deployed to where you want it to go with the updated process.
I want to be able to go to the release. Hit update processes for that release to what I just changed on any process then be able…
1 vote -
Deployment promotion with excluded steps is not persisting chosen steps
Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.
We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.
It would be great if you can persist the state of excluded steps to the next environments as part of same release?
5 votes -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
15 votes -
Tenant variables side by side
The idea is to have the tenant variables displayed vertically, with one column for each environment.
Currently, it is quite tedious to compare or copy variable values from an environment to another.6 votes -
Provide the ability to generate cryptographic strong passwords
When deploying application containers, there can be times when you want a password that no human needs to know and survives only for the lifetime of the container.
Our primary use case is generating secure keystores for certificates, etc. At container start-up, it will generate a new local keystore and we then have the ability to dynamically sign CSRs generated within the container via an external signing service.
We do not want to leave the keystore nor the certificate objects without any password, but also do not want to store the values anywhere external to the container.
Granted, we certainly…
2 votes -
Release created date (system variable)
The system variable Octopus.Deployment.Created is updated/changes between deployment to the different environments, but it would be great to have a static value for when the Release itself was created.
So i suggest a new system variable Octopus.Release.Created that says when the release was created (with the Create Release button).1 vote -
Encrypt variables using Certificate
Add the ability to encrypt variable strings using something similar to the variable filters.
Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}
3 votes -
I have multiple nuget packages that I want to deploy to a single location, can this be done with Octopus Deploy?
I have multiple nuget packages that I want to deploy to a single location (these nuget packages all make up the single Application), can this be done with Octopus Deploy?
1 vote -
Generate a deployment preview to show all variables and machines that will be utilized
I would like to be able to generate a deployment preview without creating a release. I would like this preview to show all in-scope machines and variables that will be utilized given the selected parameters for the deploy. This will help greatly in identifying misconfigured scope for variables and machine roles/environments
2 votes -
Deploy Release step should prevent picking releases from a different lifecycle
When creating a deployment 'parent' that utilizes the "Deploy A Release" step 'child', it's possible to create a 'parent' release with a 'child' release version that uses a different lifecycle. When attempting to deploy, the following cryptic error is returned:
The step failed: Activity <Child Step Name> on the Octopus Server failed with error 'The release has unresolved defects and cannot be deployed to this environment.
Once you have corrected these problems you can try again.
If the problem is related to a variable you will need to update the variables for this release or recreate the release for the…1 vote