Recently I attempted to upgrade a Stash instance to the latest version of BitBucket. The upgrade process "succeeded" but most of the repositories are no longer showing up. Before the upgrade there were 12 repos in Stash. After the upgrade only 2 show up in BitBucket. The repo files are still in the folder, and the 10 missing repos are still listed in the database when I perform the query:
select * from repository;
The database being used is MySQL. The upgrade was from Stash 2.12.0 to BitBucket 5.5.1. There were no errors or warnings in atlassian-bitbucket.log that related to the missing repos.
I'd prefer not to recreate the repos through git as was suggested to a user who was migrating to a new server. How can I point BitBucket to the repositories that already exist both within the database and on disk?
This is something that shouldn't be happening and I would consider the upgrade to have failed given that the repositories have disappeared. For that reason I'd suggest reverting to the pre-upgrade state by restoring your Stash home directory and database and attempting the upgrade again, and if you still see repositories being deleted you'd probably want to look at the Bitbucket logs to find out why that might be happening.
Premier Support Engineer
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot