General
-
Composite Step Templates
There are sets of common steps that we very often want to "bookend" all of our deployments with. One concrete example would be: sending out a Manual Intervention to confirm when all servers are confirmed live before stamping a new deployment in NewRelic.
Right now, everyone has to bake these steps into their own projects by adding the Manual Intervention step followed by the NewRelic Deployment Stamp step. If it were possible to create what I would call "Composite Step Templates" then I could define a reusable step template that was made up of other step templates. That way, instead…
891 votes -
Hide the "un-tenanted" release goup
It would be nice to hide the "un-tenanted" group of releases shown on the dashboard and project overview, if the project is configured as "require a tenant for all deployments". We don't want to delete these old releases, but they are no longer relevant to us and interfer with the information shown on the dashboard.
11 votesSee https://github.com/OctopusDeploy/Issues/issues/3169 for our plan and a workaround to get you started right now!
-
Parallel deploy throttle
Currently you can throttle the number of package aquisitions and the number of machines which will run steps in parallel.
We see issues whereby too many steps run on the same machine causing out of memory issues.
Can you please add configuration to limit the number of steps running in parallel on a single machine
12 votesGood news – we’ve started planning this work over here: https://github.com/OctopusDeploy/Issues/issues/3305 :)
-
Machine policies cleanup unavailable machines days or hours?
User interface shows hours and minutes, however the API is returning a time span of days, so for example I've set 99 hours, but the time span from the API is 2376 hours or 99 days.
16 votesThis has been confirmed as a bug so has been moved to GitHub. Thanks for the report. Please reach us on our support channels to inquire or report bugs like this :)
https://github.com/OctopusDeploy/Issues/issues/2938 -
Deployment Machine Index
Currently every step is running for every machine.
When you are deploying multiple machines, If you have a step that needs to run only one time per deployment like a global task for whole environment (for example; executing some database scripts before or after deployment.)
But we need to determine machine index to run some script only at first machine...
Regards, best wishes...
29 votesWe have begun planning to provide some mechanism to allow for “Run step on N machines”, even when the roles map to multiple tentacles. The mechanism for selecting the machine that the deployment will run under is not yet clear.
https://github.com/OctopusDeploy/Specs/issues/22 -
Better guidance for TFS users
Provide some really good guidance to help people use TFS and Octopus together.
112 votesWe’ll be building this very soon
-
Allow people to write plug-ins/add-ons with an SDK
Potentially create some kind of SDK to allow for hooking into various parts of Octopus. e.g.: permissions/users could be given a custom implementation and provided by active directory.
~~~~~~~~
Example plugins we should build:https://github.com/OctopusDeploy/Issues/issues/511
https://github.com/OctopusDeploy/Issues/issues/31258 votesWe’re going to start on this very soon. I’d love to collect more examples of what people want to do with plugins (not so much how the plugin would work/what kind of extensibility, but the actual problem you want to solve)
- Don't see your idea?