Newbie question but I could not find a definitive answer.
I have one project that I need to deploy. but deployment can go into many places
I could need to deploy a beta version into a test environment
I could need to deploy a release into one of many production environments and some of these production environments have multiple installations of our site (tenants in this context I assume)
because my flow could be
TEST->Environment 1
or TEST->Environment 2
and sometimes it’s Test2->Environment 1
because there is no specific flow and the flow changes as needed by QA and deployment slots on various environments, how do I set this up in Octopus?
Thanks for getting in touch! It looks like the channels feature (introduced in Octopus 3.2) may be the solution.
Channels allow you to deploy/promote separate releases of a single project through different lifecycles. Managing multiple active versions of a project, like beta versions or hotfixes, is a scenario that channels were designed as a solution to. It’s a powerful feature, so I would recommend checking out our documentation for in depth info and guides. The following page outlines defining a lifecycle, and defining version rules to automate channel selection based on your package version.
We also have a great channels walkthrough blog post outlining various scenarios that channels address.
I hope this helps! Let me know how you go, and don’t hesitate to reach out if you have any further questions going forward.
