1
Solved

Azure DevOps PR merge branch response

https://dev.azure.com/[]/...../_apis/build/builds/?api-version=2.

The response from devops:

{
            "id": 389235,
            "buildNumber": "389235",
            "status": "completed",
            "sourceBranch": "refs/pull/31748/merge",
            "parameters": "{\"system.pullRequest.pullRequestId\":\"31748\",\"system.pullRequest.sourceBranch\":\"refs/heads/team/realbranch-1.1\"}"
},

Now all pull request have this refs/pull/31748/merge
we'd like to filter on the source branch refs/heads/team/ for these pull requests.

can you implement fallback for refs/pull/*/merge to parameter/system.pullRequest.sourceBranch

Follow

4 replies

Votes Newest Oldest

This should be fixed in 3.4 , please try this version - https://catlight.io/downloads 

Comment
GL

1:
We have a few teams wich all use the same PR build which use  

refs/pull/31748/merge

als a branch name on the build. so that is not helpfull if i want to watch all brances of /teamname/* source branches.

2:

we are evaluating the product and this is a blocking issue for making it usefull.

3:

i'd like to filter on the value of  

system.pullRequest.sourceBranch

so i can watch the PR builds of my own team. 

Comment

Thanks for the details, I'll check what we can do. Some people might have configured the rules based on the current branch paths, we need to find a way not to break their setup.

GL

True. I cannot imaging one having value in the `refs/pull/*/merge` name

Can you provide a bit more information about this?

  • What problem do you have? Is the branch name displayed somewhere incorrectly, or you cannot filter builds by branch name?
  • Does this problem happen at some point, or was it always like that? If it happened recently, do you know if anything changed that could have caused it?
  • What behavior did you expect from the app?
Comment
GL

i replied with a new comment.

GL

i replied with a new comment.

GL

Could you please update on this?

Comment
Reply