I am planning to upgrade our 17 G Data Git repositories (about 400 at last count) with about 250 users (mysql database, running on tomcat and apache for proxy ) from 2.9.4 to 2.12 during to the compelling features in 2.12.
I was wondering if anyone could share there expierience Best Practices (other then the Upgrade Manual) do's and or be careful about some aspect.
We will be taking a snapshot of the machine running CentOS before the upgrade and a complete data backup of the repository before the upgrade.
Few questions on after thought.
1. can we upgrade the git to latest 1.9.1 at the same time when we migrate stash 2.9.4 to 2.12
2. how can we bring stash to a single user mode to test the application upgrade before rolling out to the dev.
A few general pointers.
The size of your repositories and users doesn't necessarily affect the complexity (or time) of an upgrade. It really depends on what we may (or may not) need to do to the data during the upgrade. In general we almost never touch the Git repositories, and most database changes are at the schema level, which should be fairly quick.
You should always test an upgrade on a separate server first, to make sure it continues to function in your environment. I would recommend to everyone to always have an up-to-date clone/backup of your production server that you can upgrade and test in isolation. This way you don't need to rely on a single-user mode of Stash.
You can also test the upgrade of Git on that machine as well. Related to that - I wouldn't recommend upgrading Stash and Git at the same time, purely because if something does go wrong you won't be sure what the real issue is - change one thing at a time if possible. That said upgrading to Git 1.9.1 shouldn't be an issue in any way.
so a currently we are at 220.127.116.11 so at a later day we can upgrade to 1.9.X should be fine ?
1. and would it typically be just changing the PATH to include new Git binary instead of the current 18.104.22.168 ?
2. any way to test stash in a limited user mode (say 2 or 5 users only during initial roll out.)
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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