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

Will Bamboo server 5.7.2 work with BitBucket 5.12.0?

We are using Bamboo server 5.7.2 with Stash 3.6.1. We are in the process of up grading both. Can Bamboo 5.7.2 work with Bitbucket 5.12.0 until we upgrade Bamboo to version 6.6.2?

1 answer

1 vote

Bamboo 5.7.2 uses application links version 4.1 and Bitbucket 5.12 uses 5.4.4.
Aplication links version 4.1 are not compatible with 5.x ones. For this reason some funcionalites relying on application links may not work properly. Some of the features are:

  • Triggering build events
  • New Bitbucket repository configuration in Bamboo
  • Bitbucket build notifications

Bamboo should be fine to run builds and checkout code since this communication will don't use application links but http(s) and SSH directly to the git layer.

What I suggest:

  1. Try to find an alternative where you can upgrade Bamboo and Bitbucket at same time or as close as possible. It will be easier, no tricks.
  2. If you cannot upgrade them at same time:
    1. Run a test to validate if the triggering feature will work. Although this combination is not supported, it might be possible that it works for the main features therefore not blocking you.
    2. If you face trigger issues and still need to move on with this plan, you can overcome this by removing the Bitbucket repository trigger and adding a polling trigger instead. That will assure that Bamboo will be the one pinging Bitbucket for changes. Please notice that this may overload your Bamboo server with change detection tasks that may affect the performance of your instance.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events