Automatically select the best channel when creating releases with Octo.exe

[michaelnoonan]

octo.exe create-release should automatically select the best channel for the project using the channel version rules (for Octopus.Server >= 3.2). This will ease the burden of writing custom PowerShell in build servers that are automatically pushing releases to Octopus.

Source: https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/10920663-let-octo-exe-auto-select-the-right-channel-when-cr
PR: OctopusDeploy/OctopusClients#73
PR: OctopusDeploy/OctopusClients#75

[michaelnoonan]

Release Note: octo.exe create-release command extended to automatically select the best channel for the release, or fail with details on how to create it successfully

[ErikAGriffin]

@michaelnoonan sorry for the ignorance, but does this only apply to when one is directly calling octo.exe create-release? Currently we create releases by using octo.exe push and having Octopus automatically create a release when a new package is detected, but it appears this Automatic Release Creation is not picking up on our channel rules

[michaelnoonan]

HI @ErikAGriffin - I'm sorry I missed your question. This applies any time you create a release using the octo.exe tooling. octo.exe push can create a release for you, so the same logic applies!

[ErikAGriffin]

Hi @michaelnoonan, no worries. Can you elaborate on how octo.exe push may create a release? Is there a particular flag or configuration to add in order to make it work?

[michaelnoonan]

Hi @ErikAGriffin. I've made a boo boo - I was thinking about how octo.exe create-release can also deploy that release as part of the same command. :)

octo.exe push can create a release for you as a byproduct by using Automatic Release Creation. The problem is that ARC doesn't support the logic to automatically detect the best channel based on the package version. I think this suggestion will turn into that kind of feature. https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/10776963-automatic-release-creation-to-multiple-channels

My recommendation though would be to move away from ARC which is based on a package being pushed to the Octopus Built-In Repository, and instead:

1. Push package(s) to Built-In Repo
2. Use octo.exe (or one of the build tool extensions) to create the release choosing the right channel automatically
3. Use octo.exe to deploy the release

Hope that helps!
Mike

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.