Azure-devops-docs: can you have a non deployment job not requiring approval in the same stage as a deployment job requiring approval?

[drdamour]

seems like -deployment means the whole stage needs approval and no way to run a job/task before deployment, is that the case? in fact it seems like the strategy: isn't really even required the -deployment & environment trigger the approval need alone

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
• Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
• Content: Environment - Azure Pipelines
• Content Source: docs/pipelines/process/environments.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @juliakm
• Microsoft Alias: jukullam

[WilliamAntonRohm]

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

• Azure DevOps on Stack Overflow
• Azure DevOps Support Bot

I am closing this issue now. You are welcome to @ mention me for any followup.
We hope to hear from you again.

[drdamour]

Not sure how u got that impression...the docs don’t make it clear what happens if you have multiple jobs in a stage and one is a deploy job..are they all gated deploy jobs then? Or just the one deploy job? Since the config is at the job level and the gate is at the stage level it’s not clear at all in the docs

[drdamour]

@WilliamAntonRohm can we revisit please?

[WilliamAntonRohm]

@drdamour -- thank you for clarifying your concern. Apologies for the delay in responding.

@juliakm -- please look into this issue.

[DeeptiGrover]

I have been testing diff scenarios with deployment jobs having approval checks
So, when used with other non deployment jobs in the same stage, no job of that stage gets executed unless checks are ok. Do you have any update on this please?

[juliakm]

This is spelled out on the Define approvals and checks page. I'll add a link to it from the environments page.

"Before the execution of a stage can begin, all checks on all the resources used in that stage must be satisfied. Azure Pipelines pauses the execution of a pipeline prior to each stage, and waits for all pending checks to be completed. If any of the checks fails (for example, if you reject an approval on one of the resources), then that stage is not executed."

[juliakm]

Updated https://docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops#approvals.