522 results found
-
Ability to retain release indefinitely
We often have the case, where a release has been cleared from QAT, but we continue development on QAT until the deployment date comes along a few days later. As it currently stands, there is no way for us to prevent the lifecycle retention policy from removing that release, once we start deploying the releases from the next sprint to QAT. In other words, unless a release is kept as deployed in an environment, we run the risk of it getting deleted by the retention policy.
It would be extremely helpful to be able to mark a release as "retain…
1 vote -
allow the creation of targets before they exist
It would be very nice to extend the Azure Web App style of deployment to also virtual machines. I would like to create an environment and targets in Octopus Deploy and assign roles to the targets before they exist. Then during deployment the machines would be created with Terraform, install tentacles and register to Octopus with the assigned roles. After that Octopus would deploy the actual software.
1 vote -
Deploy success report
When a deploying a release, have different greens (the green tick) when the step passed but was not deployed:
- Same version already on tenant
- Newer version on tenant.Otherwise, and since it is not evident, one has to open every of the step and, at least, check the duration of the step.
1 vote -
Allow variables in offline file drop target definitions
It would be very useful to be able to use variables to specify the Drop Folder Path, Applications Directory, Working Directory, and Sensitive variables password so they can be centrally set for a related group of offline file drop target.
Suggestion after an original support request https://help.octopus.com/t/using-variables-in-target-definition/19031
1 vote -
Master Project manual interruption step acquire all packages including those in 'Deploy release' step
When adding an interruption step to a master project (one which has many deploy release steps), it should acquire all the packages in the child deployment steps.
Alternatively run all deploy release steps in parallel (roughly 100 in my case so need to edit the max parallel projects), and have a step which allows you to accept all manual interruption, but in small blocks of 5-10 to avoid issues.
1 vote -
In a master project that includes Deploy Release steps, allow variables to override values in child deployment
In a master project that includes Deploy Release steps, we can define per deploy release step variables that will be available to steps within the child deployment's process.
We'd like to have variables on the master project level that will override the same variables child deployment's process so we won't have to do it for every step.
For example - if I have a master project with 10 deploy release steps, and each step has a db connection string variable, currently i have to go into each deploy release step and update the connection string. We'd like to see it…1 vote -
Scope private key access of the certificate step
Private Key Access which define who has access to the private-key on the target machine on the import certificate step could have a scope option.
So each environment different certificate with different user and permission1 vote -
Add tenant tag to project link on a tenant
I would like to be able to add a tenant tag to a project link on a tenant. Our tenants have 2 projects associated with them QA and Dev. Currently when I use a tenant tag the QA tester using that tenant will get access to the feature the developer using that tenant gets. This will in most cases cause the deployment to fail because the QA tester for that tenant may be completely unrelated to the developers project.
If I could put tags on a project link it would allow me to say the developer using tenant 25 gets…
1 vote -
compare builds.
The feature by which we can compare the features between one build with the other. What are the differences in the build between the two versions of the build.
1 vote -
On the dashboard use a more flex design
Currently the columns on the dashboard seem the have a fixed width.
This works fine for environments and releases but for the project icon and name it sometimes causes double lines when it's not necessary.We have 5 environments and on a 1920x1080 resolution screen almost 25% of the row is empty.
Could you change is so that the project icon and name using a 'auto' width sizing.
1 vote -
Complete the step even thought deployment was cancelled
Sometimes, developers cancel the onging release deployment. In some cases, the deployment is interrupted in the middle of step execution and changes cannot be reverted easily afterwords. For example, there is one step to restore the database and run some cleaning sql queries. The deployment was cancelled right in the middle when powershell script turned the database in a single user mode and started to restore it. Deployment was cancelled and the database was left in that state. It was required manual intervention to login and revert changes.
My idea is to add possibility to mark the step as atomic…
1 vote -
error notification to email
Receive an email when a error occurred in deployment .
1 vote -
Step Mutex for a Tenant
With multiple tenants, we use the same ARM template to lay down common infrastructure and then leverage tenant features. The problem is that if 2 or more tenants hit the ARM template step at the same time that part of the deployment fails. It would be great if we could define a step "mutex" so that only one tenant can be executing a step at a time. I've been trying to prototype as a powershell child step but I can't seem to figure out how to lookup other tenant deploys in the Octopus API.
1 vote -
Show Project Template Variables in the Release Variable Snapshot.
Currently the Release Variable snapshot screen does not show Tenant Project Template variables. It would bee good to see these so we can ensure changes are in effect before re-releasing after an update.
1 vote -
tell us WHAT CHANGED when we try to deploy to an environment and we get that awful current message "something has changed..."
my only annoyance with Octopus is when I try to push something from one environment to another and I get that dreaded "something has changed" warning.
perhaps Octopus can tell us what changed? thanks!
1 vote -
When creating a new release show notification if any variables changed since previous release
When creating a new release, if any variables have changed since the last release then a warning box should be shown saying that "Variables have changed since the last snapshot" and have the option to view these changes.
1 vote -
UI Request - Comparing differences between process-snapshots
Frequently, when DevOps is deploying a release to Production they encounter the classic Warning:
--> "The deployment process has changed since this snapshot was taken."This triggers a fire drill where dev, ops, and qa need to figure out what changed, when, and if the change is retro-actively required in previously issued releases. Generally the exercise results in dev identifying the small change and that the change is required going forward (vNext) but NOT needed last quarter's release. We have to manually download the json snapshots and load them into text diff tool. It's tedious and time consuming. It's awesome…
1 vote -
Make script arguments a multi-line textbox
When using the "Run a Script" step with a script from a package the input field for the script parameters is a single-line textbox.
It would be a lot better if the textbox was multi-line (or at the very least resizable) to make entering more than a handful parameters possible without always scrolling.
1 vote -
Allow release number version ranges to be used as a step condition
To support the introduction or removal of deployment steps while continuing to support for new builds of older configurations it would be nice to be able to set a step to only run for specific release versions.
While channels can be twisted to support this use case it requires significant setup and management on the CI server that publishes and creates the builds.
1 vote -
Allow Rolling Deployment Window Size on Advanced Deployment Screen
I see that there is a "rolling deployment" windows size on each step in the process, but that doesn't make much sense to me. I feel that I want ALL of the steps to run, but for a specified number of machines on the deploy release deployment screen. The screen that allows you to skip certain steps. An example of what I am referring to: https://app.box.com/s/x3y4n9iukx15mavz4yjasrdbt5eyae8p
Basically, if we have 20 targets in an environment, I could specify a rolling windows of 2 for that environment, and Octopus would perform ALL of the steps for two machines at a time.
…
1 vote