BitBucket Application Links to two Bamboo

Jonathan Vaughan

We are migrating some projects off an older Bamboo server onto a new server. 

 

So in BitBucket we have both Bamboo servers registered under the application links. The old Bamboo server has been marked as the primary server.

 

Now it looks like only the primary server is getting triggered when new code is added to a branch. However over time we will have migrated some projects over to the new server and would like to disable and eventually delete them off the old server.

 

What's the best way to achieve this ?

 

Edit : Further investigation showed that both Bamboos were triggered, so it must be something else causing the fail to trigger in some cases for the original Bamboo.

 

A related question is, The Pull request shows the build status, Which Bamboo server is it looking at ? and can I specify that one repo looks at the old Bamboo and another repo looks at the new Bamboo for its build status links ?

 

 

Foong

Further investigation showed that both Bamboos were triggered, so it must be something else causing the fail to trigger in some cases for the original Bamboo.

What are the old Bamboo, new Bamboo and Bitbucket Server versions? Which Bamboo isn't working with trigger?

A related question is, The Pull request shows the build status, Which Bamboo server is it looking at ? 

If both Bamboo servers send the build results to Bitbucket Server, the build status will show two build results (one from old Bamboo, one from new Bamboo).

and can I specify that one repo looks at the old Bamboo and another repo looks at the new Bamboo for its build status links ?

It is the Bamboo side that send the build result to Bitbucket Server. You will have to configure it in the Bamboo side. Old Bamboo will be configured to use one repository and the new Bamboo will be configured to use another repository.