---
title: "Discussion on \"Azure DevOps Pull Request build validation pipeline for .Net 5 project\" | Hashnode"
description: "Discussion on \"Azure DevOps Pull Request build validation pipeline for .Net 5 project\". When working in teams, we always want to ensure that any new PR (Pull Request) doesn't break the main build pipeline, deploy broken code or cause unit test cases to fail. We never want the PR to be merged to the master/main branch and then revert it ..."
url: "https://hashnode.com/posts/azure-devops-pull-request-build-validation-pipeline-for-net-5-project/6095ad3321068818a5c606bf"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Azure DevOps Pull Request build validation pipeline for .Net 5 project](https://kumarashwinhubert.com/azure-devops-pull-request-build-validation-pipeline-for-net-5-project?utm_source=hashnode&utm_medium=feed)

When working in teams, we always want to ensure that any new PR (Pull Request) doesn't break the main build pipeline, deploy broken code or cause unit test cases to fail. We never want the PR to be merged to the master/main branch and then revert it ...

May 7, 2021 · 5 min read · kumarashwinhubert.com  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#net](https://hashnode.com/tag/net)
-   [#yaml](https://hashnode.com/tag/yaml)
-   [#build](https://hashnode.com/tag/build)

## Written by

[Kumar Ashwin Hubert](https://hashnode.com/@kumar-ashwin-hubert)

@kumar-ashwin-hubert · India

  
[View profile](https://hashnode.com/@kumar-ashwin-hubert)

I'm a software consultant who loves to build projects and share my learnings on this blog.

## Responses 2

Markdown supported · ⌘↵ to post

[Kumar Ashwin Hubert](https://hashnode.com/@kumar-ashwin-hubert)

[Aug 7, 2022](https://hashnode.com/posts/azure-devops-pull-request-build-validation-pipeline-for-net-5-project/6095ad3321068818a5c606bf/comment/62f00d5fdfc2b155658842c7)

[Andrew Lindeman](https://hashnode.com/@LrngToFly) I am not sure of why that is happening. Ideally multiple PR validations can be triggered in parallel, provided the build agent has parallel jobs configured.

Can you please confirm my understanding about your problem :

1.  Developer 'A' is creating PR #1 for say `feature-branch-1` to `master`.
2.  Developer 'B' is creating PR #2 for say `feature-branch-2` to `master`.
3.  You are noticing that the PR #1 build cancels after PR #2 is created for a different branch?

[Andrew Lindeman](https://hashnode.com/@LrngToFly)

[Aug 8, 2022](https://hashnode.com/posts/azure-devops-pull-request-build-validation-pipeline-for-net-5-project/6095ad3321068818a5c606bf/comment/62f00d5fdfc2b155658842c7#reply-62f10126e3a3793580e0613b)

Hi! Thanks for responding. To be clear, this is a on premises Azure DevOps server. When I google "parallel jobs", I found some links referring to hosted Azure DevOps.

But yes, the scenario you list is indeed the scenario that is causing my developers headaches.

Thanks!

[Andrew Lindeman](https://hashnode.com/@LrngToFly)

[Aug 4, 2022](https://hashnode.com/posts/azure-devops-pull-request-build-validation-pipeline-for-net-5-project/6095ad3321068818a5c606bf/comment/62ebd024f583cc2636e53327)

I have a validation build configured for Pull Requests. When a build is ongoing due to a PR #1 and another developer creates PR #2, the build from PR #1 is cancelled mid build. This is driving my devs nuts. Do you know of a way to stop this (allow the build from PR #1 to complete before starting PR #2's build.) Many thanks!
