Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Shadow Merge Commit Build Status plugin not detecting pull request builds


We've got TeamCity building our pull requests and publishing the results back to Bitbucket Server 6.3.0 using the Commit status publisher feature. This is working fine, but has minimal visibility within Bitbucket.

So I've tried installing the Shadow Merge plugin, but it doesn't detect any pull request builds from before it was installed, or any new builds triggered after it was installed. Is there something else we need to configure? The documentation seems to indicate all you have to do is install it and it will handle the rest.

2 answers

1 accepted

0 votes
Answer accepted

Actual issue was that TeamCity's "Build Pull Request" feature actually builds the tip of the branch, and not the pull request.

Once we changed the Branch Filter in TeamCity to this


it works as expected

Hi Brad, 

this might be super outdated, but I stumbled accross your post while looking for some help with a similar problem. 

I installed the Add-On onto our Bitbucket Server, and ever since it letting me know that it cannot detect any recent Shadow Merge builds, and it is not building anything when a pull request is being created. 

Our build server is Bamboo, and I checked the git repo, it contains all those refs/pull-request/[id]/merge references that the Add-On seems to require. But I have no clue what to do or configure to make it fly and trigger some build from those refs. 

Do I have to create a separate build plan in Bamboo, do I have to adapt the existing ones running our tests? How do I tell shadow merger what commands to run in order to run our tests on the merge result of the PR-branch and the target branch? 

Would be super cool if there were any documentation on this, but unfortunately, there isn't. 

So... thank you in advance. 

All the best, 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events