We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.
It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")
Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.8 votes
Lifecycles are the way in which users can define what environments are used in what projects
In our project we have 2 branches - trunk and patch - both of which produce packages for Octopus and use semantic versioning when creating the Octopus release in the build. I would like to specify a build from the patch branch explicitly so that when packaging off the trunk my release would be 1.24.102948 but when packaging off the patch branch my release would be 1.24.102949+patch. My workaround is to use the pre-release metadata so my patch builds are producing octopus releases 1.24.102949-patch.29 votes
A flag on the Email template step to send the email as High Priority. We use the Email template step (when any step fails) to notify that the deployment failed and it would be more convenient if we could set the flag for high priority. I could create my own powershell step, but I thought the out of the box email template step could use this feature.82 votes
Despite the flagrant ballot stuffing, I agree it has value, so I implemented it in 4.1.1 (https://github.com/OctopusDeploy/Issues/issues/4031)
We have "major deployments". At this time we have to deploy all our applications (~ 70) at once. So it would be nice to have a possibility to deploy all projects from environment-1 to environment-230 votes
In Octopus 2018.2 we shipped the Deploy Release Step (https://octopus.com/blog/deploy-release-step/deploy-release-step), which allows you to create “bundle” projects to address exactly this scenario.
I hope that helps!
Current configuration (v4.0+) uses dropdown control for Releases list.
Previous implementation had combo box control and it allowed to do a quick search for large releases lists.
Would love to have this feature back since currently it is not possible to do a 'contains' search among differently named releases.30 votes
This feature is still in Octopus in 4.1.4 we have made a bit easier to find: https://github.com/OctopusDeploy/Issues/issues/4080
Have an option to disable the Guest/Account question on the splash screen as I always want to login with an account.
Logging in always takes a few clicks with the Guest/Account question. As a dev I never want to see the guest option. Can there be a way of preventing it showing - perhaps via a cookie such as "Remember this choice"?3 votes
Hi Paul! You can do this already by disabling the Guest Authentication Provider: octopus.com/docs/administration/authenticat..
You can do this via the UI in more recent versions of Octopus, or you can always do it through the command-line interface. Details are on the page.
When you list the releases for a product you can see the Version and when it was assembled, but not the release notes. We have this connected to the git commit log so we easilly can see what is being deployed. Right now we have to click each item to see this information25 votes
The release notes column has been re-introduced in the latest builds.
Provide an additional option in Configure dashboard to allow selecting project groups instead of just individual projects. This way if an additional project gets added to the group it automatically appears on your dashboard rather than having to look for and add new projects to the filtered list.20 votes
This was implemented and released in 2018.5.3
The search is case sensitive when searching for a script module in the "Include a Script Module" dialog from the Process page.
I think this should be case insensitive.2 votes
This was fixed in 2018.8.10.
The Set-OctopusVariable (and its counterparts for other scripting languages) should support an -IsSensitive flag such that if a variable is marked as sensitive it will not leak into a log.40 votes
This was implemented in Octopus 2018.5.2
I would love to see built-in support for Terraform (https://www.terraform.io/). Deployment steps for each Terraform operation like "plan" and "apply" and also a Terraform backend plugin for storing state.57 votes
We have recently provided support for some simple Terraform steps as of `2018.3`
Read up in our docs for more details (https://octopus.com/docs/deploying-applications/terraform-deployments) and let us know what you think! We certainly expect to extend the functionality of these steps based on usage and demand.
Ideally variables can be read without expanding the browser to both windows - probably a bug
A fix for this will be available in the next 4.0.11 release
The new Docker features debuting in recent versions of Octopus are really promising, and I'm excited by the Docker Compose RFC published late last year.
Kubernetes is becoming increasingly popular as the production deployment environment of choice for containerised applications. It offers functionality very similar to Azure Service Fabric, in terms of auto-scaling and self-healing of services and applications, but is based around container images rather than zip files.442 votes
Kubernetes and Helm support has been added as a preview feature in 2018.8.0. We will be working on these steps in future releases based on the feedback from this release.
Allow Octopus to download from Maven repositories servers instead of the Build-in Octopus repository.3 votes
I just updated to the new 4.0.3 version of Octopus. I do NOT like the process to skip deployment steps. It is hard to follow and see what is going on and takes way longer than the older versions. Please change this to something more like the older version where I can see all the steps and easily click on the ones I want to skip.
One of the people on my team couldn't even figure out how to skip the steps it was such a pain to find.6 votes
Excluding steps has become unmanageable, please revert to what you had before... causing us hell.1 vote
Right now only manual intervention steps cannot be skipped during a custom deployment. It maybe good to be able to mark any step as unskippable.15 votes
This was implemented in Octopus 2018.4: https://octopus.com/blog/octopus-release-2018.4
in our Deployment processe we have 25 steps.
on old version we was able to check or uncheck for example steps 1 to 10. in order to deploy first part or second part.
but now in the new version the exclude steps is not as esay. you have to open select box, select one step. the selectbox is closed. then you have to open it again and select the next step... 10 times... it is lot longer thant only chech on uncheck visible checkboxes.
i would expected an easier way but now it is an harder way...1 vote
The users view that pages user into n number of pages, makes it a hassle to find a user when you have 100 or more users.
I would like to be able to search for a user, and search across username, displayname and email address.14 votes
This ability is available as of Octopus 4.0
As it is now if you can change the deployment process, you can also set scripts to run on the Octopus Server. We want people to be able to change the deployment process, but not to run scripts on the Octopus Server. A permission or feature-toggle to restrict that option would be great.24 votes
We have implemented this in 2018.1 (https://github.com/OctopusDeploy/Issues/issues/4070). However it will be superseded by https://github.com/OctopusDeploy/Issues/issues/4158 in the future (subscribe to that issue to stay updated).
- Don't see your idea?