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

Your Points Tracker
  • 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
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?
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

Bamboo not triggering build for branches when code is pushed to stash

I have a bamboo plan with linked repositories and the builds are triggered with Remote Trigger. The builds are kicked off whenever a code is pushed to stash.  

Now, I created 2 more branches in the plan as feature1 and feature2.  Both the branches are sharing the same repositories and trigger as master. Whenever the code is pushed into stash, I see that a build is kicked off in all the plans which is as expected. 

From past few days, I'm seeing an issue where a build is kicked off for the master  and feature1 and not for feature2 branch. The feature2 branch is not detecting the changes from stash where as feature1 and master detects the changes and a build will be kicked off. When I kickoff a manual run for the feature2 branch I can see the commits(under commits tab). 

WorkAround -> If the bamboo is restarted the issue will be resolved but I hit the same issue after few days. And we don't want to restart the bamboo every time we see this issue. 

Can anyone suggest a solution for this problem or a better workaround?

Thanks in advance. 

1 answer

1 vote

Hi @SheshaChandra ,

If you want to troubleshoot the issue, you need to identify:

If you are using Bamboo and Stash (Bitbucket Server), you should be considering replacing your repository configuration in Bamboo from Git to Bitbucket Server. By doing it so, you would benefit from Application Link between the two application.

When you create a plan that uses a Bitbucket Server repository as Host, Bamboo uses the 'Bitbucket repository triggers the build when changes are committed' trigger option by default. If the plan already exists, you need to configure the trigger manually.

In other words, when a commit is made to your repository in Bitbucket Server, Bitbucket will check if there is an Application Link with Bamboo. If so, it will get the URL defined in the application and send a POST event to Bamboo notifying it about changes in repository.

If Bamboo has a plan that consumes the repository in question and the trigger 'Bitbucket repository triggers the build when changes are committed' is defined, Bamboo will act on the event received triggering a new build (if configuration is met).

Just for the record, what is the Bitbucket Server (formerly Stash) and Bamboo versions you are running? This information helps on narrowing down issues ;)

Kind regards,

Suggest an answer

Log in or Sign up to answer
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 ...

203 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