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!


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
Community Members
Community Events
Community Groups

Bamboo remote trigger | triggering all the build plans

We are using Bitbucket server and Bamboo in our solution. I have a server side hook configured in Bitbucket's file system. I use following command to get the latest commits and based on the path of files changed, I trigger the Bamboo build plans.

COMMITS=`git show --name-only --format=tformat: HEAD^..HEAD`;

I am using "/api/rest/updateAndBuild.action?buildKey=" rest api endpoint to trigger the builds.

I have three build plans which should be triggered as follows-

  • Build-plan-1 - Should be triggered if changed file's path contains "src/build-plan-1"
  • Build-plan-2 - Should be triggered if changed file's path contains "src/build-plan-2"
  • Build-plan-3 - Should be triggered if changed file's path contains "src/build-plan-3"

I am not sure why, but even a change in "src/build-plan-1" is triggering all the builds. I have tried passing dummy commits and the shell script is running fine.




0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events