Add global steps
I have come to find almost all of the project steps for my applications follow a general pattern:
Deploy package
Do clean up
Configure
Send Email
If I could encapsulate steps similar to Variable sets so that I can include them where needed, this would actually cut down on my maintenance requirements by a ton. I see this as kind of a rules engine. So...
"When a package is deployed..." do a step before the process is allowed to continue.
"When a project is released..." do a step after the process is done.
All of these would be able to consume project and release variables much like Variables sets can consume variables in other sets. In particular, all my "project has deployed" emails are exactly the same. Only the subject changes on whether or not it was successful. This feels like needless duplication and is confusing for whomever inherits my job in the future if they don't happen to have whatever custom tools I've developed to make managing this easier.
Michael H
shared this idea
-
Anonymous
commented
Is this a duplicate of this item? https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/5923829-add-the-ability-to-add-child-steps-an-or-multiple
-
Sam “Betty” McKoy
commented
Events could allow for interesting things permissions wise - eg adding manual intervention without the ability for developers to remove it from projects.
-
Sam “Betty” McKoy
commented
-
Sam “Betty” McKoy
commented
other ideas that might work
* nestable global steps (currently we can import shared steps, would be nice if those steps could contain multiple steps)
* reusable process templates (eg custom like normal or use a predefined process).That said some kind of event system could be more powerful, just might not be so clear on what is happening (eg you'd want it somehow visualised in each project so you can figure out why things happen).