We have just migrated from TFS 2018 to Azure DevOps Services and we're having a hard time trying to figure out the new Azure YAML pipelines.
We want to be able to:
- Run a build/test pipeline when a PR is pushed to
We've already accomplished this by creating a dedicated YAML pipeline that only builds and runs the tests (no publish artifact or anything). This pipeline is triggered by a "Build Validation" branch policy on the
- Run the full CI/CD pipeline that will build, test and deploy to DEV and QA environments when a commit is pushed to the
We've already accomplished this by using a multi-stage pipeline triggered by any change in the branch. Although we're not entirely happy about the duplicated tasks here (this has exactly the same tasks to build and test the project as the above pipeline).
- Deploy to our production-staging environment when a commit is pushed to the
We're stuck here. We're not sure how to do this without creating yet another new pipeline that will do exactly the same as the previous one, but targeting our staging environment. We want to "build once, deploy many". This was easy using TFS build and release pipelines (I guess this is what Azure DevOps calls "Classic Pipelines", right?)
How we can accomplish this workflow without needing to create several similar YAML pipelines, but also following the "build once, deploy many" pattern?