We are currently using Stash (3.11.2) which has good amount of data. Planning to migrate it to Bitbucket 4.2. We also would like to migrate the operating system from Fedora to RHEL along with this move. What is the best way to migrate Stash (in Fedora) to Bitbucket (RHEL) with all existing data, history, comments and the uers?
Below you will find more detailed steps:
You can find all steps to upgrade Stash from version 3.11.2 to the latest Bitbucket version on this documentation: https://confluence.atlassian.com/bitbucketserver/bitbucket-server-upgrade-guide-776640551.html
However, we always recommend you to try to upgrade your system in a staging environment first to avoid outages. Also have a backup from your Stash and the database.
Please keep in mind that upgrading from Stash to Bitbucket Server will disable all user-installed add-ons, whether they are 3rd-party add-ons from Atlassian Marketplace, or your own custom add-ons. User-installed add-ons will need to be checked, upgraded and enabled again once you've finished the upgrade process. You should check the marketplace listing for 3rd-party add-ons to determine if there is a release that is compatible with Bitbucket Server 4.2. Unless they have been updated to work with Bitbucket Server 4.2, existing add-ons (or plugins) that use the API interfaces that have been removed in Bitbucket Server 4.2 will not work. Similarly, custom add-ons need to be upgraded for Bitbucket Server compatibility. See the documentation on how to update your add-on for details.
In case you are curious about about why we are changing the brand from Stash to Bitbucket Server feel free to check this FAQ.
Don’t forget to have a look into the Supported Platform Documentation before you follow to the upgrading process to avoid any incompatibility.
Lastly, can you confirm if you are only planning upgrade the version of Stash to Bitbucket server, or you also will change the database version or the server hardware as well?
If you are planing to migrate to another server, please check this documentation.
In case you are planning to upgrade the Stash Server and also move to a different machine, we strongly recommend you to first move to the new server with your currently version of Stash and after everything will be running properly, then go ahead to upgrade the Stash version.
There are no special instructions. Copy the $STASH_HOME to the new server (if needed) and start up a new Bitbucket Server and point to the copied copy. If you need to move the database too, make a copy of the DB and point 3.11.2 to that DB first before the Stash upgrade.
Thanks all for your responses.
Will follow the tips shared and come back to you.
BTW, we are planning to upgrade Stash server and also move to different machine. Will it be any issue in case I setup a new server with Bitbucket 4.2 and copy the data from existing Stash server?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot