Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Run additional builds upon Pull Request update

I am not sure if I am being thick but not quite sure how to configure Bamboo (or Bitbucket Server) to run another branch build when a pull request is updated with additional commits.

I have setup a Plan with Brach Plans that are automatically created by new Pull Requests. I have also configured Bitbucket Server trigger on the plan.

Currently only a single build is done on the pull request when it is created. I would like additional builds to occur as Bitbucket detects new incoming commits and let the auto-generated pull request branch plan know so it can run another build.

Is this possible?

 

1 answer

1 vote

Hello @Sohrab Hosseini,

Can you please explain your Bamboo - Bitbucket Server configuration and what do you mean by configuring "Bitbucket server trigger on the plan"?

When you use option to create plan branch when PR created Screen Shot 2017-07-20 at 12.22.08.pngBamboo automatically creates plan branch linked to that PR. As I understand you already have this configuration.

Then when you make a commit to the same branch Bamboo should build that branch as usual. If it doesn't happen please check your Trigger configuration, it should be like this:

Screen Shot 2017-07-20 at 12.24.10.png

Hi @Alexey Chystoprudov

I am not sure what happened but after deleting and re-creating the plan a few times, it seems to now have worked without any modifications. I did not see any useful logs in either servers to indicate what the problem was early on.

Out of interest, why do you have more options in your screenshot than I do, on Trigger conditions:

Screen Shot 2017-07-20 at 9.53.57 pm.pngI am using Bamboo 6.0.1 and Bitbucket Server 5.0.1.

We have few internal plugins to add trigger conditions, they're not production ready yet

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you