We have a lifecycle setup that requires the DEV environment first, then either TST or UAT, Then STG and finally PRD
Due to bug fixes the release numbers are out of numerical sequence. We have a 3.4.2.7 release in DEV and TST (initial environments), we are attempting to deploy release 3.4.1.2 to PRD.
The release we are about to publish to PRD environment has been deployed to the previous environments, but we are not getting the option of PRD in the “Deploy To” box.
I have attached a word document of screen shots of each of the areas to better describe the issue.
The easiest work around is having multiple channels.
Since you have 3.4.1.2 needed in prod, your issue is the lifecycle FORCES all previous steps to apply.
To get around this, my company has another channel tied to another lifecycle called ‘Production patch’. This allows us to have Phase 1 point to the equivalent ‘Staging’ environment then to Production in phase 2.
It is a very quick fix for you and in the overview page it would be clean as well.
Thanks for getting in touch! And thanks @T3 for your suggestion. Your suggestion to use channels in this way is a great solution. Channels are commonly used for bug fixes to avoid having to promote them through each individual environment.
