Moving RTC SCM content to another repository?
I have a need to move code under Jazz SCM from one repository to another and wondering if there is a good method of doing so. My source is RTC 3.0.1.1 and the destination is RTC 4.0.5.
I have figured out how to move work items but the code has me thinking. I would like to try temporarily "friending" the new repository and attempting a deliver to the new project(s). Has anyone tried that approach? Is there any other approach that would allow me to preserve my baselines and snapshots? Cheers! |
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 04 '14, 6:35 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
To replicate code from one RTC repository to another, you would use the distributed delivery (see https://jazz.net/library/article/535). But it is likely that you will not be able to do so directly from an RTC-3.0.1.1 repository to an RTC-4.0.5 repository, so you would have to do it in two stages:
- upgrade your RTC-3.0.1.1 repository to RTC-4.0.5 - deliver from your upgraded RTC-3.0.1.1 repository to your RTC-4.0.5 repository In order to replicate your baselines, you will need to deliver each baseline individually (clearly, scripting this up will be in order, unless you are very patient). Also, there is no way to automatically replicate snapshots, so you will have to recreate them in the target repository. Bryan Miller - Integration Developer selected this answer as the correct answer
Comments
Bryan Miller - Integration Developer
commented Feb 04 '14, 6:40 p.m.
Much obliged Geoff. Upgrading 3.0.1.1 to 4.0.5 is not an option - which is part of the reason for the move. Is dumping to a changeset archive an option?
Geoffrey Clemm
commented Feb 04 '14, 6:49 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Just add another step:
Bryan Miller - Integration Developer
commented Feb 04 '14, 6:56 p.m.
That sounds painful but the best option yet. Thanks Geoff!
we just went thru this process. it is very painful. but u can use distributed SCM to do the data movement (same version restrictions)
Bryan Miller - Integration Developer
commented Feb 05 '14, 10:20 a.m.
Thank you Sam. That is very helpful. Did you use wrapped CLM command lines or full-on Java API?
I wrote custom java code. I needed to 'copy' a project from one repository to another. and much is not accessible from the commandline.
streams and workspaces were the next to the last component.
builds & defs need the workspaces to exist first.
Public URI was the issue I was mentioning in the last paragraph above.
showing 5 of 6
show 1 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.