Difference between revisions of "SVN Migration"
Msteghofer (Talk | contribs) m (→Step 1: Upgrade your SVN client) |
Msteghofer (Talk | contribs) (Monday -> Tuesday) |
||
| Line 1: | Line 1: | ||
== Migration == | == Migration == | ||
| − | During the night between | + | During the night between Monday, 18th June and Tuesday, 19th June the whole SVN repository content (Toolkit, Gimias, Suites, etc.) will be moved from a local UPF server (https://svncistib.upf.edu/repos/toolkit) to an Amazon Cloud server (https://svn.gimias.org/svn/toolkit). From that moment on the old server will still be reachable, but with read-only access. So before changing the server URL of your local checkouts you won't be able to commit changes to the repository nor will you get any updates from your colleagues. |
So you will have to do an operation that is called "relocate". This will tell your SVN client the new URL of the SVN server that corresponds to your local checkout. So for future operations it will know, where to get updates from and where to commit your changes to. | So you will have to do an operation that is called "relocate". This will tell your SVN client the new URL of the SVN server that corresponds to your local checkout. So for future operations it will know, where to get updates from and where to commit your changes to. | ||
| Line 7: | Line 7: | ||
== Step by Step Instructions == | == Step by Step Instructions == | ||
| − | While the actual relocation of your checkout (Step 3) has to be done on | + | While the actual relocation of your checkout (Step 3) has to be done on Tuesday 19th June or later, you can do some preparations before (if and when you have time) to make sure the transition next week goes as smoothly as possible and your work doesn't get interrupted. Especially if you haven't updated your repository for some time and have local changes, then during [[#Step 2: Update|the update in Step 2]] there can be conflicts that may take you a while to resolve. |
The steps presented here have to be done for every checkout you have on your machine (e.g. once for Gimias-1.3.0, once for Toolkit-Trunk, once for Cardio-Suite etc.). | The steps presented here have to be done for every checkout you have on your machine (e.g. once for Gimias-1.3.0, once for Toolkit-Trunk, once for Cardio-Suite etc.). | ||
=== Step 1: Upgrade your SVN client === | === Step 1: Upgrade your SVN client === | ||
| − | ''Note: This step can be done before | + | ''Note: This step can be done before Tuesday.'' |
Make sure that you have a reasonably recent version of your SVN client. Below you can find a table of minimum versions for the relocation to work properly: | Make sure that you have a reasonably recent version of your SVN client. Below you can find a table of minimum versions for the relocation to work properly: | ||
| Line 30: | Line 30: | ||
=== Step 2: Update === | === Step 2: Update === | ||
| − | ''Note: This step can be done before | + | ''Note: This step can be done before Tuesday.'' |
Do an update to make sure you have a checked out revision greater than r18722 (any revision after 7th June 2012 15:28:42). | Do an update to make sure you have a checked out revision greater than r18722 (any revision after 7th June 2012 15:28:42). | ||
=== Step 3: Relocate === | === Step 3: Relocate === | ||
| − | '''Note: Don't do this before '' | + | '''Note: Don't do this before ''Tuesday 19th June 2012 9 AM (CEST = GMT+2)'' or your checkout will be broken (you may have to delete it and check it all out again)!''' |
==== SVN Command-Line client ==== | ==== SVN Command-Line client ==== | ||
Revision as of 08:31, 14 June 2012
Contents
Migration
During the night between Monday, 18th June and Tuesday, 19th June the whole SVN repository content (Toolkit, Gimias, Suites, etc.) will be moved from a local UPF server (https://svncistib.upf.edu/repos/toolkit) to an Amazon Cloud server (https://svn.gimias.org/svn/toolkit). From that moment on the old server will still be reachable, but with read-only access. So before changing the server URL of your local checkouts you won't be able to commit changes to the repository nor will you get any updates from your colleagues.
So you will have to do an operation that is called "relocate". This will tell your SVN client the new URL of the SVN server that corresponds to your local checkout. So for future operations it will know, where to get updates from and where to commit your changes to.
If you have a reasonably recent version of your SVN client (see first step) then this won't take more than 10 minutes per checkout and you won't have to worry about local changes. They don't affect the relocate and can be committed after the relocation process.
Step by Step Instructions
While the actual relocation of your checkout (Step 3) has to be done on Tuesday 19th June or later, you can do some preparations before (if and when you have time) to make sure the transition next week goes as smoothly as possible and your work doesn't get interrupted. Especially if you haven't updated your repository for some time and have local changes, then during the update in Step 2 there can be conflicts that may take you a while to resolve.
The steps presented here have to be done for every checkout you have on your machine (e.g. once for Gimias-1.3.0, once for Toolkit-Trunk, once for Cardio-Suite etc.).
Step 1: Upgrade your SVN client
Note: This step can be done before Tuesday.
Make sure that you have a reasonably recent version of your SVN client. Below you can find a table of minimum versions for the relocation to work properly:
| Client | Recommended Version | Working Version | How to check version |
|---|---|---|---|
| SVN Command-Line client | >= 1.6.12 | >= 1.5.0 | svn --version |
| SmartSVN | >= 7.0.2 | >= 7.0.2 | "Help" -> "About SmartSVN" |
| TortoiseSVN | >= 1.7.7 | >= 1.6.3 | Right-click in the explorer -> TortoiseSVN -> About |
If you have a version that matches the "Working" requirement, but not the "Recommended" requirement, the relocate will still work, but it may take much longer. For versions even older than the "Recommended" requirement the relocate might still work (no guarantee!), but it might take even longer and local changes might get lost.
Step 2: Update
Note: This step can be done before Tuesday.
Do an update to make sure you have a checked out revision greater than r18722 (any revision after 7th June 2012 15:28:42).
Step 3: Relocate
Note: Don't do this before Tuesday 19th June 2012 9 AM (CEST = GMT+2) or your checkout will be broken (you may have to delete it and check it all out again)!
SVN Command-Line client
Execute the following commands:
cd /path/to/my/local/checkout svn switch --relocate https://svncistib.upf.edu/repos/toolkit https://svn.gimias.org/svn/toolkit .
SmartSVN
- Choose "Modify" -> "Relocate..." from the menu
- In the Relocate-window:
- Replace the old URL https://svncistib.upf.edu/repos/toolkit by the new one: https://svn.gimias.org/svn/toolkit
- Click OK
TortoiseSVN
- Right-click on your checkout directory and from the context menu select "TortoiseSVN" -> "Relocate...".
- In the Relocate-window:
- Replace the old URL https://svncistib.upf.edu/repos/toolkit by the new one: https://svn.gimias.org/svn/toolkit
- Check the option "Include externals", if it exists in your version of TortoiseSVN.
- Click OK
Step 4: Update
Do an update (like in Step 2).
While usually this won't actually find any new updates on the server (you just did an update 5 minutes ago in Step 2), for some clients this steps may be necessary to update external links (especially in Gimias and Suites, not in the Toolkit) before you can do commits again. For all repositories apart from the Toolkit, do it just in case.
