In Azure Devops, I have always wondered how does the release pipeline associates the stage to the branch the artifact is built from.
I mean,
- When I build from the "dev" branch, it produces the artifact "artefact" and the release pipeline kowns that it is for the "DEV" stage
- When I build from the "preprod" branch, it produces the artifact "artefact" (same name!) and the release pipeline kowns that it is for the "PREPROD" stage
- When I build from the "prod" branch, it produces the artifact "artefact" (same name, again!) and the release pipeline kowns that it is for the "PROD" stage
In fact, it is set in a filter in the "Pre-deployment conditions":
In each "stage", click on the "Pre-deployment condition" and on the artifact filter condition, tell what branch should trigger this stage