Skip to content
← Product Feedback

What problem could Octopus Deploy solve for you?

Product Feedback: Deployments

Categories

(thinking…)

Allow creating a Channel Version Rule that applies to all Steps

In Octopus 3.2 the Channel Version Rules only apply to explicitly selected Package Steps.

When adding a new Package Step, you need to remember to add that Step to all of the Channels that apply, otherwise when creating a Release, none of the Version Rules will apply to that new Package Step.

What if you could create a Version Rule that applied to ALL Package Steps as an alternative to being explicit?

This could be more convenient, and safer-by-default, when people follow a consistent convention for versioning the packages in their Projects.

62 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

Michael Noonan 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
  • Andreas Caravella commented  ·   ·  Report

    This would be a great addition and make deploys much safer! We've just spent a good deal of a day hunting a bug that came down to a missed version rule (and hence, we deployed a pre-release version of a component in one of our steps).

  • Sam Kompfner commented  ·   ·  Report

    Agreed. A 'select all' and a 'deselect all' option would be handy. And the use of checkboxes so it is quicker to select multiple steps rather than go through the drop-down each time would be preferable.

  • queil commented  ·   ·  Report

    I think it would also make sense to expose that in Octo.exe create-channel so I can automatically create channel with all steps picking up the right package version.

  • Mike Jacobs commented  ·   ·  Report

    I'd like to suggest that the option be to be able to select all otherwise unselected steps from the project. I have a project with over 40 nuget unpack steps, but 10 of them would be in one version rule, and the rest in an "and the rest" version rule (and new ones would go in the "and the rest" pile.)

  • Anonymous commented  ·   ·  Report

    This could be achieved by including the ability to have variables in versioning rules?

  • Anonymous commented  ·   ·  Report

    We have 3 Channels each on a 25 step package. We wish to apply the same version rule for each step on a channel. This would be very convenient for when we put a new version in a channel