We are running builds in Devops, and using the octopus plugin to send the build to octopus. We want to be able to identify in Octopus which builds came from the release branch vs which ones came from the test branch. Is there any way to do this?
Reason being on release night all we see is a list of builds with version number. If we could see for example the letter ‘R’ appended to it then we would know that is a release build. At the moment we can’t see that so need to rerun all builds before we deploy just to make sure we have the right binaries.
Thanks for getting in touch!
While you cannot add tags to Releases in Octopus, you can create them under different Channels to easily differentiate which Octopus Release was created by a Devops Build that came from a Release Branch or a Test Branch.
Ultimately your dashboard will look something like this:
In that screenshot you can see two channels:
Channel Release which only has the Octopus Release
0.0.1. Your devops builds would only create releases in this channel when you are building from the Release Branch.
Channel Test which has plenty of releases with the format
*-Test*. Your devops builds would only create releases in this channel when you are building from any non Release Branch.
Channels in Octopus are a big concept, so I strongly recommend you to take some time to read our documentation and our walkthrough blog post:
Hope that helps,
This is excellent – much better than adding tags!
I managed to do this in Devops by selecting the channel from the “Create Octopus Release” step for our web deploy.
However, with our Java deploy we don’t seem to have that option and I was wondering how I can do it. With our Java deploy we are using a “Push zip file to Octopus” step in the Devops Release. This
plugin doesn’t have the option to choose a channel. Are you aware of anything I can do with this:
Thanks for your help…
Like you mentioned, in that process you are just pushing a package to Octopus but you are not creating a release from it. That’s the reason we you can’t see any channel-related option.
So the question is where are you creating this release from? Is Octopus creating it automatically when your pushed package reaches Octopus? If that’s the case, then I would strongly suggest you to move the Release Creation part of the process to a build step just like in your other project.
Let me know if that makes sense
It seems obvious now you point out what the solution is! I was working on the assumption that the release creation was part of the package push.
I have added the release creation step and now works very well…
Thank you for your help with this!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.