Skip to content
← Product Feedback

What problem could Octopus Deploy solve for you?

Product Feedback

Categories

(thinking…)

Implement Process Templates

It would be nice if Octopus supported process templates on a per project basis. This would allow the user to define multiple templates for any given project and select the template to use when the release is created. There are a couple use cases for this:

1) Deploying multiple versions of projects that contain different components. For instance:

I have MyProject v1.x which contains components A & B. This version is in the final stages of QA and is getting bug fixes that need released directly into the QA environment on a daily basis.

Meanwhile I have MyProject v2.x which is under active development and contains an additional component C but no longer has B. This needs released to Dev on a daily basis.

Currently in Octopus I could not created releases in parallel for these two different versions because my v1.x would not have a 1.x version of Component C and would be missing component B because it would be using the latest process.

If there were process templates I could create one for each "major" version of the my software and be able to create and deploy releases for each in parallel.

2) Testing updates to your deployment process. Right now if you make a change it is immediately applied to newly created releases whether it's been tested or not. If I could create a template I could choose not to use it for releases created by my build server and only use it on releases I've manually created for testing purposes.

I'm sure there are other use cases but these are the two major ones I see.

15 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Harald Sømnes Hanssen commented  ·   ·  Report

    I would like to have a preset multistep process template which can be adjusted across projects.

  • Christian Andersen commented  ·   ·  Report

    I also like this idea. My use case would be that I have a project where I normally have rolling deployments. But sometimes for bigger updates I have to shutdown the whole application and deploy all in parallel or wait to start up the application until everything else is finished. For this case I would like to have two deployment processes assigned to one project. When creating the release I want to choose the deployment process for this release.

  • Matthew commented  ·   ·  Report

    I can see this being a really nice feature. The scenario we run into would be in our production environment. We have a weekly deployment process for production support and a monthly deployment for new features. The monthly deployment needs to do things that the weekly deployment does not. This means when we deploy on the weekly basis we have to make sure we "skip" some tasks to prevent issues or long wait times for the product to be deployed. If we had the ability to specify a template and then deploy against that template it would save a lot of work and human error prevention as well.