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!


Branch Plan Auto-Merge. How to configure to happen on remote agent .vs. bamboo server

When using the automatic merging (Gatekeeper in this case) the merge happens on the Bamboo server itself .vs. the remote agent for the plan. 

Is there a way to configure Bamboo so it performs the merge on the remote agent configured with the plan?

Unless I'm seeing this wrong, automatic merging happens redundantly (twice) as it merges on the bamboo server (I'm guessing to verify it merges properly) and then moves to the remote agent and performs the same merge again.  Why?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 04, 2019 • edited

it merges on the bamboo server (I'm guessing to verify it merges properly) 

Yes, it is merged in Bamboo server to check if there is a merge conflict. Since the Bamboo server have the repository cache, the test merge is faster in Bamboo server side instead of the remote agent.

It is also a immediate check in case of a situation when all the remote agents are busy performing other builds.

There isn't any setting to disable this merge check in Bamboo server.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events