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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,883
Community Members
 
Community Events
176
Community Groups

Handling Pull Request Approvals in Bamboo

Hi All,

Using BitBucket Repository (Cloud) and Bamboo Server 6.2.2

I have a scenario where I need to do the following.

 

1. PLAN-A - Want to check that the feature branch merges cleanly with the branch it was started from. Doe some compilation and basic checks.

  • A pull request is opened.
  • Bitbucket sends a trigger to Bamboo with a Web Hook.
  • Bamboo creates a branch for PLAN-A and builds it. 
  • Every time a new change is added to the branch the branch plan is executed. 
  • Results are posted to Pull Request

I have configured a web hook on Bitbucket like this.

https://MY_BAMBOO/rest/triggers/1.0/remote/changeDetection?planKey=MY-KEY&skipBranches=false

I have a Bamboo Plan with a remote trigger set. The plan creates a branch on pull request creation. This seems to work fine. If there are changes then the branch plan is created and executed. 

2. PLAN-B - Merge the change into the branch it was branched from. Doe some compilation and checks. Push the merge back to BitBucket.

  • Bitbucket sends a trigger to Bamboo with a Web Hook.
  • Bamboo creates a branch for PLAN-B
  • The branch is merged into the base branch.
  • Bamboo builds it.
  • On success the merge is pushed back to BitBucket which closes pull request.

 

This kinda seems to work. Sometimes I feel like it says no changes detected. Also I cannot seem to configure a GateKeeper merge strategy. The option is simply not there. 

 

Has anyone else had a scenario like this one?

0 comments

Comment

Log in or Sign up to comment