General
-
Release Manager
Often times with our release we are deploying multiple configurations. With the way octopus stands now you would have to manually go and deploy each project. What we did was created our own tool that uses the API that allows us to deploy multiple projects at once to a particular environment. Something like this might be nice to build into Octopus Deploy itself.
3 votesA feature that will do just this will be available in the next few weeks in version `2018.2.0`
Take a look at our blog post for more details!
https://octopus.com/blog/deploy-release-step/deploy-release-step -
Allow "Configure Features" in "Run Script" steps
I want to be able to say, transform a json file, and then run a script.
Right now the only way to do that is by putting your script into a nuget package, naming it "publish.ps1", using the "Deploy a package" step and targetting it somewhere, then enabling configure features.
1 voteThis is under development now.
We are adding all the configuration transform features to the Script Steps.
The plain is to ship this in the August 2018 release.
-
Allow Azure powershell steps to run on servers other than the OD server
The Azure powershell steps run on the Octopus server, which is good for ease of getting up and running and small projects, however it is not great when you've got a lot of steps and a lot of projects. This is especially painful when you've got lots of steps that take time. If a cloud service takes 3 minutes to deploy, and you've got 6 to deploy, that blocks the server for at least 18 minutes.
This would probably be even more useful if implemented in conjunction with https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6316906-support-run-on-any-tentacle-model-for-deployment.
I know that some people would prefer still to keep…
5 votesWe have started this, follow https://github.com/OctopusDeploy/Issues/issues/4158 for details
-
Allow updating of existing Step Templates via the Import feature
The ability to import step templates from other locations (e.g. Octopus Library) is awesome, but if someone updates the step template the import process can not be used to update the copy I have in my Octopus server. I'm forced to delete the step template and re-import it. Obviously if I have N projects that rely on the step template I'm now stuck because I can't delete it when projects are using it.
Since I can technically update the powershell script and change parameters and so on inside of Octopus Deploy UI itself, importing of existing step templates should just…
24 votesThanks for voting on this suggestion. We’re working on a number of changes to the step template library, and this is one of them. It should ship in the next month or so.
-
Previous deploy variable for environment
I would love to have a variable available that is similar to Octopus.Release.Previous.Number but instead list the previous release number for the specified environment not the project.
9 votesNew variable names will be in 3.0.
https://github.com/OctopusDeploy/Issues/issues/1496
- Don't see your idea?