When updating a Step Template - update across all Projects
I want to use template-all model, where all projects consists only of step templates, to provide central management of deployment process. But when i modify step template, I need to manually go into every project and into step and click "update".
I think it would be better to use TeamCity model, where template can only be inherited and not changed inside project, or cloned from template if changes needed. Or provide the ability to one-click update all steps that uses the template (even better ask for it after click on Save button).
I'm going to end up with 30+ projects, all using the exact same setup consisting entirely of imported Step Templates. A "Project Template" feature would be hugely helpful; failing that, I need some way of auto-refreshing all imported steps.
Vanessa Love
shared this idea
Great news! We have shipped this feature in Octopus 3.12. https://octopus.com/docs/deploying-applications/step-templates/updating-step-templates
-
Igor Kudrin commented
Description says it is only planned:
Planned (not exhaustive list just some I like on the UserVoice site)
* Update step template across all projects
-
Amjad Khoja
commented
This has become critical as we have more templates and cannot update the usage one by one. Any help would be appreciated.
-
Bruce Foust
commented
Please allow either an update all or update some/one.
1: I would like the update available option in a couple extra locations. If this would show on the Step templates list, the Project process page, as it does on the usage page it would be easier to see when a step is out of date.
2: Allow us to flag a version when we determine it is not to be updated so it will stop showing as an update available. -
Tristan Bates
commented
Please!
-
Anonymous
commented
Please add this feature ASAP. We already have 200 or more projects and growing
-
Anonymous
commented
This would be realy nice. We have arround 109 projects at the moment....
-
Andy
commented
We have 35 projects with a standard "Release Done" email - when we update that email's contents (not often thankfully), having to go through all the projects one by one to update the step is a bit of a pain.
If there could be checkboxes column on the Usages screen with an "update checked" button, or something similar, that would be great.
Thanks.
-
Paul
commented
Because this was so tiring to do when there were lots of steps using the step template I wrote some CodedUI automation in Visual Studio to just run through the process of updating all the references. Kind of brute force but it worked and saved me 100s of mouse clicks until this feature is added.
-
mwoffenden
commented
Absolutely essential!
Very much interested in the full auto update feature, as it's very tedious to have to open each step and hit Update -- esp for a deployment that has a lot of steps.
-
Lineshen Moodley
commented
+1 this would be a really useful thing to have
-
Cenon
commented
+1 on this it is annoying to have to update each project just because you've changed a template
-
Claes Lindblom
commented
I think it is a must have to be able to mass update all steps in a project.
-
Dan Bishop
commented
I'd really like to see the "update everywhere" option when updating a Step Template. We are using some Pre-Deploy Powershell scripts, and it is a real drag to have to go manually update each individual deployment step to get the updated template every time we need to fix a minor issue/bug in our scripts.
-
-
Anonymous
commented
The new step template feature is great, but I can already see a usability issue looming. If a template is used across multiple projects (which is the entire point, right?) and then the template is modified, the administrator has to navigate to each project using the template and modify it in order for that project to use the new version. The template page should automatically update all dependent projects if possible, or at the very least display a list of links to all dependent projects for easier navigation.