General
-
Add ability to indicate whether Windows Service should be started on deployment
In some environments we do not want a Windows Service started after it is deployed. In the current Octopus.Features.WindowsService_BeforePostDeploy.ps1 file the service is always started. It would be great to have a flag that could prevent the service from being started.
159 votes -
Add XmlPoke feature for setting random config values using XPath
It would be nice to be able to set random values in the config files using an XmlPoke type feature where you could specify XPath expressions that point to values in the config file and then specify values to set them to.
Here is an example to set the compilation debug to false:
XPath: configuration/system.web/compilation/@debug
Value: falseThis would allow setting random values throughout the config file without having to use config transforms.
127 votesThis is now possible with the structured configuration variables feature (https://octopus.com/docs/deployment-process/configuration-features/structured-configuration-variables-feature#xml) shipped in Octopus 2020.4
-
Rather than allways taking the "latest" version of a package, can we scope the step to within a particular version range
When you create a release, Octopus default to picking up the latest version of the available packages.
We have multiple forks of our packages, and we need to be able to restrict a package step so that it is limited to a particular version range of the package, for example:-
If we have a major version 1 of a package on a step,
If we later create a fork and do work on a major version 2,
We do not want the next octopus release to pick up major version 2 - we want to limit the scope of the…
34 votesThis ability is available via the Channels feature as provided in Octopus Deploy 3.2 (http://docs.octopusdeploy.com/display/OD/Channels).
Channels can specify version rules that define what packages are included in that release. -
Allow me to choose which environments a project uses / per project environments
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 votesLifecycles are the way in which users can define what environments are used in what projects
https://octopus.com/docs/deploying-applications/deployment-process/projects/lifecycles -
Support semver 2.0 build metadata in the release version.
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 votesThis feature has now been provided in Octopus Deploy 3.4.0 (https://octopus.com/downloads/3.4.0)
See the recent blog post covering these changes https://octopus.com/blog/semver2 -
Audit trail and report for permissions\role changes of users
Recently we have been audited and one of the questions asked of me was to provide a control for how permissions are managed. At the same time provide me with evidence that you periodically review permission changes using a system generated report. This would be very simple to implement using the same audit structure currently used for the deploy process and it would make auditors happy.
7 votesPermission and team changes are currently audited
-
Add "Substitute variables in files" feature in "Run a Helm update" step
In "Run a Helm update" step we need: Enabled Features -> Substitute variables in files
Why?
For example we need to create configMap for our helm-chart. App config locate in this chart, so we need replase all #{values} by values from project scopeStep helm_install:
1. download chart
2. Substitute variables in files (choose location)
3. in custom script (deployment step) create configMap for our podsIf this feature doesn't exist: we need another step where we download app config and substitute variables and use this file to create configMap
3 votesThis has been fixed as part of the issue documented at https://github.com/OctopusDeploy/Issues/issues/6476.
-
allow the Email Step to flag the email as High Priority
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 votesDespite the flagrant ballot stuffing, I agree it has value, so I implemented it in 4.1.1 (https://github.com/OctopusDeploy/Issues/issues/4031)
-
Add the Octopus CLI to HomeBrew
We're working on a few Mac minis to be our iOS build servers. We use (among other things) Homebrew as our package manager. For a variety of reasons, we need the Octopus CLI tool installed on these Mac Minis. You guys support MacOs, but it doesn't look like you've added the CLI to Homebrew.
While I was tempted to add it myself, I figured I'd start with suggesting it here.
1 voteThe CLI is now available via HomeBrew. See https://octopus.com/downloads/octopuscli#macos for instructions.
-
promote a whole environment
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-2
30 votesIn 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!
-
Quick search for Releases no longer available in Octopus v4.0+
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 votesThis 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 votesHi 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.
-
Show Release Notes as a column directly on the Releases page for a product
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 information
25 votesThe release notes column has been re-introduced in the latest builds.
-
Configure dashboard to allow selection by project group
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 votesThis was implemented and released in 2018.5.3
-
Make "Include a Script Module" search dialog case insensitive
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 votesThis was fixed in 2018.8.10.
-
Set-OctopusVariable to support -IsSensitive flag
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 votesThis was implemented in Octopus 2018.5.2
-
First level support for HashiCorp Terraform
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 votesWe have recently provided support for some simple Terraform steps as of `2018.3`
https://octopus.com/blog/octopus-release-2018.3#terraform-support
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. -
BUG: Allow library variable names to be viewed on one screen
Ideally variables can be read without expanding the browser to both windows - probably a bug
Screens:
https://ufile.io/nf3ps15 votesA fix for this will be available in the next 4.0.11 release
-
Support for Kubernetes
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 votesKubernetes 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.
-
Support for external Maven Repositories (Java packages)
Allow Octopus to download from Maven repositories servers instead of the Build-in Octopus repository.
3 votes
- Don't see your idea?