It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×11,924
×889
×173
×46

question asked: Jun 04 '12, 1:30 p.m.
question was seen: 4,909 times
last updated: Oct 12 '17, 12:47 p.m.

Related questions

FAQ - How this Forum works

Importing a subversion repository with many branches and components

1
Adam Elliott (13●2●4) | asked Jun 04 '12, 1:30 p.m.
edited Oct 12 '17, 12:47 p.m. by David Lafreniere (4.8k●7)

We have a subversion repository with over 40k revisions that we want to import into RTC. Internally our repository is split into five parallel directory structures with their own trunk/branches/tags, which correspond fairly well to RTC components. There are approximately 100 branches we want to keep [at minimum]... each of these branches is present in each of these directory structures.

Since migration is only via the eclipse client, and it only does one branch into one component at a time, this means running the migration 500 times...

Note of those 100 branches, maybe only 10-15 are really active, but even restricting that means running the migration over 50 times. This just isn't very feasible.

Is there some way of automating this? A command line or Java API? Thanks.

Accepted answer

2
permanent link
Michael Valenta (3.7k●3) | answered Jun 07 '12, 3:06 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
As you say, the Subversion importer only supports importing a branch at a time and there is currently no command line support. There is no official API for the Subversion importer but it would certainly be possible to to write a Java based utility that simplified the import of multiple branches.
David Lafreniere selected this answer as the correct answer

One other answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
paulo xavier (21●4●6) | answered Oct 04 '12, 4:54 p.m.

I have the same problems and a I have 843 CVS repositories to migrate to RTC scm.

Each one have a lot of branches and tags and should be preserved in the migrations process.

By the way, we have one of the largest instalations in the world in Jazz Enterprise Deployment .

The lack of a an automated process compromises the migration.

This is a very common problem and must have automation. 

Your answer

Register or to post 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.