Migrating Version Control Systems

[Bill Faulkner]

OK, I was wondering if there was an easy way to change the version control inside EA from one system to another. It appears to me that on must change it for each and every package inside one's project. Since we have several projects, each with 100+ packages this is very tedious. Anybody know of a better way?

TIA

[HowardB]

Hello Bill,

The functionality that you are asking for is something that has not yet been implemented in EA.

I believe the easiest way for you to acheive your goal, is to export your entire model to XMI, (in the browser, right-click on the model root node(s) and select "Export model to XMI"), then create a new, empty model and Import from XMI.  That will create a copy of your model, without any version control.

Then, in the new model, define your VC configuration and apply version control.  

EA version 7.1, released yesterday, now has a command "Add Branch to Version Control".  This should make the process somewhat less tedious.

If your model is stored in a third-party DBMS, you probably should re-create it as an EAP file, as an intermediate step.  Once you are satisfied that the EAP file is complete and version controlled as you desire, then use the Data Transfer facility to overwrite the old model in the DBMS.

p.s.  I am curious to know which VC product you are changing to...

regards,
Howard Britten.

[«Midnight»]

Howard,

What about projects with several models (i.e. multiple root nodes)? Would you just repeat this for each?

If so, am I right in assuming that when you recreate the model you'd first import the default (first) model. Then you would create a 'dummy' root node and import the next model 'on top' of it, causing it to be replaced with the next model from the source project. You'd then repeat this process until all the models were added.

Make sense, or am I talking - yet again - though my hat?

David

[Bill Faulkner]

Just some more information for people - We are using a private model with version control for each package. We are currently using Borland's StarTeam but are migrating to Telelogic's Synergy for version control.

We have two main models that must be controlled - one has about 100 packages, the second has about 200 controlled packages.

So I had a question or two about the new "Add Branch to Version Control" feature. First what does this do? I assume its something like use the following VCS for me and all my children. If I do as Howard suggests (exporting the project and then re-importing it), would using "Add Branch to Version Control" create seperate XMI packages for each package?  Any additional info would be helpful.

I will pull down 7.1 in the next few days and try a few things and if I find anything of note, I'll let everybody know.

Bill Faulkner

[«Midnight»]

Bill,

I suggest you look at this thread before you go too far: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1204278260.

David