We are creating our stash integration platform, for testing changes before we implement them on production.
We would like to restore most of the data from production to this system and a hand full of repository, most, because we do not want to restore i.e. directory settings or application links.
So we made a Database backup and are trying to restore some single tables, but because of a missing DB schema we do not really know which table we need.
Actually we restore the following tables:
project.sql sta_normal_project.sql repository.sql sta_activity.sql sta_repo_activity.sql sta_pr_activity.sql sta_pr_comment_activity.sql sta_pr_diff_comment_anchor.sql sta_pr_merge_activity.sql sta_project_permission.sql sta_pr_participant.sql sta_pr_rescope_activity.sql sta_pr_rescope_commit.sql sta_pr_rescope_request.sql sta_task sta_comment AO_BD73C3_PROJECT_AUDIT.sql AO_BD73C3_REPOSITORY_AUDIT.sql
Most works fine, but we have some trouble with the pull request view.
How do other handle this?
We recommend you do that by backing up Stash on the production server and then restoring it on to the Integration server using the backup client. Have a look at the docs below. This methodology is detailed and should work:
This will though restore your production directory settings or application links – which you can remove once it is up and running.
I hope it helps.
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