Book a Demo

Author Topic: Version control  (Read 3389 times)

Martin Walke

  • EA User
  • **
  • Posts: 51
  • Karma: +0/-0
    • View Profile
Version control
« on: January 29, 2010, 01:17:07 am »
Hi all,

I'm trying to integate EA with version control software. At the moment I'm using VSS but willl eventually be using Subversion. The actual app is immaterial with my question, which is.....

I have an already created model that I want to have the version control software manage. How can I add the model so that all the packages (nested ones included) are managed by the version software?

Hopefully I don't have to go to each package and add them seperately!   :-/

TIA
Martin

Jeff B

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Version control
« Reply #1 on: January 29, 2010, 08:11:55 am »
Martin,

You can add a set of nested packages to version control using the Package Control -> Add Branch to Version Control... menu option from the context menu on the desired top-level package.  This also creates a branch configuration file (xxx.EAB) that other users can use to check out the whole branch using the Package Control -> Import a Model Branch... option.

Best regards,
Jeff

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Version control
« Reply #2 on: January 29, 2010, 06:59:34 pm »
Martin,

The downside of using the "add branch" is that is gives the xmi files a generated (id) name where with the manual procedure you can decide for yourself wich name the xmi file should have (defuaults to the name of the package).
This is useful if you want to do something with those files (for example get a previous version back) outside of EA.

But you don't have to go all the way immediately. What you can do is control only some of the packages, and control then control the top level "root package".
Then as the need arises you can control additional individual packages.

Geert

PS If you decide to manually control the packages, go bottom up. Saves you a lot of time  :)

Martin Walke

  • EA User
  • **
  • Posts: 51
  • Karma: +0/-0
    • View Profile
Re: Version control
« Reply #3 on: January 29, 2010, 08:41:31 pm »
Thanks guys.

I'm not sure that I want to add a branch if it means the name becomes (un)predictable. We currently use an exported xml file to produce other documentation from the model so that may be a problem.

Looks like i'll have to resort to adding the packages bottom up.

Thanks again