We’re using Octopus v2018.9.4
We recently had a need have the same package deployed multiple times, which is the 1st and 2nd lines in the following image:
The third line is a separate package.
Creating release is choosing from the alpha release for the second package and the third package (expected), the first line is choosing the production release.
We can override the behavior if we are doing a release from the Octopus Deploy UI
However, this is part of an automated pipeline, so that’s not useful.
We’ve done something like 500 releases with packages on lines 2 and 3 working with the pre-release tag/channel working perfectly! The change here is the new step (which was copied from the working 2nd step, and only some powershell and step name were changed)
Why would Octopus Deploy not auto-choose the same release for the same package? What can I do to get this working?
Note: the package being deployed multiple times is a command line utility that uses different parameters at different steps.