Migration of self-managed Jira and Bamboo servers to Atlassian Cloud

[vmandapati]

Sir,

We have a solution with self-managed Jira server and self-managed Bamboo server, both deployed in a customer data center. As Atlassian stopped selling and upgrading Server licences we are evaluating the option of migrating both to Atlassian Cloud.

Please confirm the below :

1. While Jira can migrate to Jira Cloud , does Bamboo also has Bamboo Cloud , so that both Jira and Bamboo can be in Cloud ?

2. The target servers for deployment are still On-prem, so can we deploy to on-prem from Atlassian cloud ?

3. What are the costs of migrating to Jira cloud and Bamboo Cloud ?

warm regards,

Rajeev

[Nic Brough -Adaptavist-]

For questions 1 and 3, the simple answer is that there is no Bamboo for Cloud. You wold probably want to look at replacing it with Bitbucket Pipelines if you want to move your build servers to Cloud

The "cost" of migrating Jira to the Cloud is whatever you need to pay someone to do the move for you.

On question 2, yes you can use Bitbucket pipelines to deploy to your servers behind your firewall, as long as you give them a route to do so

[vmandapati]

Thanks Nic. for your reply.  Is Bitbucket being projected as a potential CI/CD tool replacement for Bamboo ? Rather than BitBucket, I prefer Bamboo tool itself but in Atlassian Data Center.  A little bit background on our current solution. It is a custom solution (platform) with two solution components - Jira and Bamboo both self-managed are are deployed in customer data center with target deployment platform as servers hosted on-prem. These components are wired (via applications links) between them and also wired with other another Bamboo server instance that does the builds. 

Option 1 - Both solution components - Jira and Bamboo on Data center. Need to check cost implication as I came to know that Jira Data center starts with 500 user license and we do not need that many users. Rather, Jira Cloud has license plans monthly/annually with smaller user license buckets like 16-25, etc where we do not have to pay for unused users. 

Option 2 - Jira on Cloud and Bamboo on Atlassian Data center with applications links setup between them and Bamboo on Atlassian data center deploying to target server on customer data center. 

Out solution is planned to be offered as a service that is technology/tool agnostic, like say Jira talking to Jenkins server instances and still be able to deploy to target servers  on-prem in customer data center.

Please suggest the feasibility of Option 1 and Option 2 above and give your advise.

regards,

Rajeev

[Nic Brough -Adaptavist-]

I would prefer to think of Biitbucket-pipelines as an Atlassian build tool, rather than a Cloud replacement for Bamboo.  It's quite different.  But yes, many of us could replace Bamboo with it.  There's no migration path though, you'd have to rebuild all the builds.

Both of your options will work fine.  Option 2 will need a little thought about how Cloud gets through your firewalls to talk to Bamboo, bit that's not complex.