You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Bitbucket has announced that the application for the Server license has closed and recommended customer to move to Bitbucket Cloud.
Correct me if I am wrong that if we were to move the code to Bitbucket Cloud, we have no control of the VM and its backup plan?
We want to have the visibility of the VM that host our code with svn and currently we manage it with AWS EC2.
So, is Bitbucket Server in AWS AMI with new license still available for new customer ?
Please refer to AWS AMI doc Launch Bitbucket in AWS manually | Bitbucket Data Center and Server 7.20 | Atlassian Documentation
Hi @Andrew Liew
Welcome to the Community!!
The new installation of the server is not available
DC installation is available as a single node or multi-node
May I know the use case for you to use the server now? none the less it's not available just asking. Go with DC
@Vishwas My team has decided to go for Bitbucket Cloud. We plan to do a PoC first with Free using an atlassian account (my company email) and then request the subscription change from Free to Premium where we migrate the rest of the code and integrate with Jenkins.
Is this possible?
Hi @Andrew Liew,
If you are looking for a backup solution, do Bitbucket Data Center. This guide should be helpful https://confluence.atlassian.com/bitbucketserver/disaster-recovery-guide-for-bitbucket-data-center-833940586.html.
You should be aware that Bitbucket Data Center could be challenging when writing your scripts due to limited public API.
For example, at Gitprotect.io for Bitbucket Cloud version, we have backup and recovery for:
In the case of Bitbucket Data Center, it's limited to code stored in git repositories and metadata like pull requests and webhooks.
If you want to backup and restore metadata via API there is a huge difference between what you could do on the cloud and the dc version. The APIs from the cloud version are not available in the dc version.
You can't backup and restore the same information, not to mention simple cross-recovery even if the products look similar.
Plus you have API call limits that could block your users if your scripts doesn't work correctly and have larger number of repos to backup: