I want my Stash test server to have the same or as close to the same data that production has when I run it through the upgrade process. I am on 2.0.3 and wanted to know if I dump and load the external database from prod to test db, and over write the STASH_HOME from prod to test excluding the stash-config.properties file will this work? The data migration wizard instructions doesn't have enough information on it to make feel comfortable using it to push from prod to test without potentially causing me a production issue...if anyone has a method they use for populating their test environment I would appreciate it.
The approach you described will work, with one caveat. If any git writes (pushes, background tasks) are in progress on your production environment, the copy step may include partial writes and can result in an incoherent git repository. You can avoid this by shutting down Stash before taking the db dump and performing the copy, if that's an option for you.
From Stash 2.7 onwards you can use the Stash backup client to take a backup of your production environment and restore that on your test 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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot