I am planning to upgrade Stash from 2.4.1 to 3.3. I am using SQL server database.
As the Stash-backup-client is only supported starting from Stash 2.8, I have to manually backup Stash data, then upgrade Stash.
Is there any consideration before this upgrade? and how a rollback can be done in case issues with the upgrade.
What Lars mentioned is correct. I'd just like to comment on a few points on this thread.
I hope this is helpful.
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