Inheritable Templates
There should be the possibility to create project templates which can be chossen when creating a new project. This should then not only copy everything, but keep the reference to the template. So when something is changed in the template, all projects based on this template should be updated as well.
Steps coming from a template should not be editable in a subproject, but there should be the possibility to disable a specific step in a specific project.
Also there should be the possibility to add other steps between "template steps" to customize the process.
Teamcity has a simillar model.
Yannis
shared this idea
We have no specific work in progress at the moment, but we are actively listening in this area. Please continue to share specific scenarios.
-
Stephen Schaff commented
This would make life in Octopus deploy much easier. I have a bunch of projects that are the same, except for the variable values. They all deploy to Kubernetes the same, they all use the same processes and run books. But when I want to add a step to the process, I have to go add it to each and every project and make the change. <sigh>
It gets tedious... -
Anonymous
commented
any update on this?
-
Dylan
commented
We have micro services, I have 30 APIs that need a deployment process update.
I shall now be spending my morning going through each one, doing the same thing over and over again. This shall be a sad morning.
A similar model to the TeamCity 'Template' approach would be great, with the ability to 'Force Update' all the inheriting projects from the template. I.e. I still don't want to have to update lots of projects to the latest template, I want to do it once and have all projects automatically updated.
-
Aaron Roydhouse
commented
This would be great. The TeamCity model works well, with the ability to use a Process template. but then in the Process using the template, you can disable Steps or insert extra Steps (before/after/between any template Steps).
-
Alex Gurman
commented
Would be nice!!!!
-
Rob
commented
I've been searching for an hour to see if Octopus has this support. I hope that this is still in the pipeline. Templates automate process maintenance.
-
Michael Le
commented
Do we have a release timeline for this feature?
-
Michael Le
commented
+1
-
Brian Herbert
commented
You will find a nice diagram to illustrate this suggestion if you look here:
http://help.octopusdeploy.com/discussions/questions/10468-run-a-step-after-every-deployment#comment_41799080 -
Brian Herbert
commented
This is not really a template because you want to "keep the reference". It should be called Inheritable Projects.
-
Niklas Arbin
commented
We have a microservice environement where all deployments are very similar. This would be the number one thing to make working with Octopus better for us
-
Kenneth Truyers
commented
-
D Lemos
commented
Very good idea and it should be implemented in the future.
-
Warren Rumak commented
Please consider doing this one -- almost 50% of my Octopus use is the repetitive, error-prone work of making identical or near-identical changes to a number of projects.
