I have a Release pipeline with ~20 stages. Depending on the kind of release we are doing, we decide to run some subset of these stages.
Running each stage is expensive and we do not want to run it unless absolutely necessary.
Is there a direct way to disable some stages at the time of kicking off the release, so that we execute only the absolute necessary stages in the release?
If not, then what is the best programmatic way of achieving this behavior?
Currently, there is no option to disable the stages based on the conditions. I'd suggest you can submit feedback for this feature
As Daniel Suggest you should create separate release pipelines for your use case
Another option is to you can define that conditions in the task level with your stages to skip.
For Example,
You have 3 stages:
Each Stage have 2 task:
Let say if you don't want to deploy in QA.
Then you can define your custom condition for the 2 Tasks in QA in order to skip the execution.
You can refer my answer for working with custom conditions.
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments