Package Versions with 2 Channels?

Legacy Execution
1

Hi,
I am creating 2 VSTS Builds to trigger releases to Octopus

VSTS Build 1 is master branch which deploys release to Channel with UAT & Production Environments when master branch changes
VSTS Build 2 is develop branch which deploys release to Channel with DEV & SYSTEST Environments when develop branch changes

My concern is will the deployed octopack packages get muddled. How will the release in Octopus distinguish the packages built from the develop branch to those built from the master branch?

My MSBuild arguments set the Package vesion to OctoPackPackageVersion=$(Build.BuildNumber) in both Build 1 & Build 2 definitions.

Will this cause an issue?? If so, what’s the best way to manage it?

Thank You
Phil

2

OK so let me know if this is correct…

I made my Build 1 (Prod & UAT) build packages with name ‘-master’ at the end.

Then in my channels i used a tag to include/exclude packages with ‘-master’ in the name.

This hopefully prevents one channel from using the packages from another channel.

Is that the best way to do it?
Thanks
Phil

3

Hi Phil,

Thanks for reaching out! You nailed it with that last reply: Tagging your packages with -master and -dev and then adding a tag rule to your channel is the right approach.

Cheers,
Dalmiro