Hi,
-
I post this question again, as I’m looking for help in my case.
-
There’s a behavior I’m noticing when I skip steps for deployments. If I skip steps in an environment, and then promote to the next environment, it doesn’t preserve the step skipping. Here’s a scenario where this breaks a deployment pipeline.
-
In my scenario there are more than 70 micro services which some time only 20 of them will be deploy to the pre - > prod. Each time I need to exclude all besides the relevant 20 projects, and here some times human can do mistakes.
-
We’ve tried to use manual intervention step, but it’s overhead.
-
Is there another way (via script or other variable modification) to prevent this from happening in Octopus? Ideally, I would expect that when you manually skip the steps in the first environment (TEST/PRE), that Octopus would preserve those skips for all promotions up the ranks. How do enforce my deployment pipeline here?
Thanks
Ofer