CODEWITHSUNDEEP
azureazure-devopspull-requestbranching-and-merging
Raja Shekar
Raja Shekar

Reputation: 23

How to Trigger a pull request using script or pipeline once build is successful from azure devops

I have a requirement. Whether it is possible or not I don't know Requirement: I have three branches 1. Master, 2. Dev, 3. Test. Here every time new code is committed to dev or test and we create a build to execute the code. Now the requirement is I don't want to merge the code to Master branches unless build is success for master. When build is successful then only PR will be triggered and code will be merged to Master Branch.

Master build ---> Success ----> Then merge code with Master Branch. Is this possible, without merging the new code into main branch, how can we test the new code from master branch in the build. And if that build is success then only PR has to take place and merge the code in master branch.

Upvotes: 0

Views: 1195

Answers (2)

Leo Liu
Leo Liu

Reputation: 76928

My requirement is Once the normal build is success then only PR has to be triggered and merge the code with master branch. Can this be achievable with powershell/bash script that can trigger a PR from pipeline (Build)

I'm pretty sure what you are looking for is branch polices Build validation instead of trigger a PR from pipeline.

You may not fully understand the logic of Build validation and PR.

What you want to achieve is to protect the master and not merge the PR on the branch to the master until the build verification success.

So, the key point is to verify the code after the PR merge, instead of triggering the PR after the build is completed. Otherwise, your build will always be the code on the master before the merge, and this verification will be meaningless.

Adding the Build validation on the master branch, which will trigger the build pipeline when we create a pull request. When we create a PR, it will create a temp commit to save the merged code and build pipeline will checkout this new temp commit to build. If build successful, then we could complete the PR, otherwise, we could not complete the PR, the master code would not be updated.

That should be what you want.

Upvotes: 1

blockingHD
blockingHD

Reputation: 463

Azure DevOps uses branch polices to achieve this which you can read about Here

Upvotes: 0

Related Questions