Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Azure DevOps Pull Request build validation pipeline for .Net 5 project" | Hashnode

Feed/

Discussion

Kumar Ashwin Hubert

May 7, 2021

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 ...

kumarashwinhubert.com5 min read

#devops #net #yaml #build

Responses2

Markdown supported · ⌘↵ to post

Kumar Ashwin Hubert

Andrew Lindeman 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 :

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

Aug 7, 2022

Andrew Lindeman

Aug 8, 2022

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

Aug 4, 2022

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!