| << Back to previous view |
|
[QB-2869] Subversion relocate working copy
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 6.1.36 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 2 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Is it possible to do a svn relocate before checking out a subversion repository?
What we would need: When we perform a change of the domain of the svn server from e.g. svn.something.org to subversion.otherdomain.net then the repository url will change from e.g. https://svn.something.org/svn/foo/trunk to https://subversion.otherdomain.net/svn/foo/trunk. Quickbuild should then be able to perform a working copy relocation. How this can be done: First check the current location of the working copy. If entered url has a different repository part from the one in the working copy metadata (in my example this is https://svn.something.org/svn/foo = the repository root) do a "svn relocate NEWURL" (where NEWURL is the entered url) for svn > 1.7 and a "svn switch --relocate OLDURL NEWURL" for svn < 1.7 I think that can be done just at the beginning of the checkoutByRevision method in the SvnRepository class. If you have questions, please don't hesitate to ask. Thanks, Alex |
| Comments |
| Comment by AlSt [ 10/Jul/17 06:27 AM ] |
|
Anything new on this issue?
The old domain is still in place on our side, but as its DNS server is very old and unreliable it would be nice to be able to switch to the new domain some time soon and it would ease up the process a lot if such functionality is in place. |
| Comment by Robin Shen [ 10/Jul/17 08:46 AM ] |
| I think this is a quite edge case, and QB can get around this by cleaning the workspace. We'd like to include it into QB8 if it gets more votes. |