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

If master is updated with new commits and one of its child branch ( hotfix ) is outdated

Scenario : Master got new commits merged from INT however hotfix branch which was created long back has old master commits ( excluding the new master commits came from INT )  So if we merge or delete the hot fix branch and still the bamboo plan consider those commits which came from int as new commits and takes those files. So is there a way to make bamboo to just get those commits but not to consider in the build.

1 answer

0 votes

Hi @Dineshmathiazhagan

If you delete the source repository branch, Bamboo will not run a build for it but It will disable its related plan branch.

If you want to merge it to master and not have a build triggered for it, you can:

  1. Use the Bamboo Exclude Changesets feature Repository >> Change Detection Options >> Exclude Changesets with the following pattern:
  2. Edit the merge commit to having "[skip]"on its message

Please let us know if that is what you need.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events