Book a Demo

Author Topic: Shared EAP File with TFS  (Read 4332 times)

DaniM

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Shared EAP File with TFS
« on: June 16, 2009, 06:24:05 pm »
I have a customer that tries desperately to manage the EAP file using TFS 2008.
HG has no problem to configure EA to connect to the correct workspace and to define packages that are version controlled. The problem arises when several developpers are supposed to use the model.

Problem is that the EAP must be checked out in order to open it and the customer has configured TFS not to allow multiple checkouts. When the EAP file is checked in, then one can not open it and we receive an error message related to the jet engine saying that it is locked and the model can not be opened.

Using a private model for each user and getting the packages from the source control is not an option, since the model as a whole must also be controlled, sine it may have sevral versions.

Can you help?
Thanks
Dani Mannes

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Shared EAP File with TFS
« Reply #1 on: June 17, 2009, 08:10:19 am »
See http://www.sparxsystems.com.au/WhitePapers/Version_Control.pdf.  Probably see the first section and the appendices.  http://www.sparxsystems.com.au/downloads/whitepapers/EA_Deployment.pdf may also help.

But ultimately, you can't version control the eap file itself.

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Shared EAP File with TFS
« Reply #2 on: June 17, 2009, 11:40:48 am »
See : http://www.sparxsystems.com/uml_tool_guide/version_control/applying_version_control_to_en.html - for clarity on Simons point. More speifially see the note at the bottom.

DaniM

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: Shared EAP File with TFS
« Reply #3 on: June 17, 2009, 03:47:39 pm »
Thanks for the reply, i have read the documents. I understand that the root model can also be saved as a XMI file and be version managed.
This can solve the versioning of model structure (=> package composition). We sould therefore create a branch in TFS that contains the root model XMI and all related package xmi files.
The question is now regarding the update of a model when sombody changes a package xmi. EA gives the option to get latest. Is there an option to make sure that the model i have is always up-to-date => some kind of auto reload as soon as sombody checks in a modified xmi file. very similar to the case where several users work on the same EAP file, where in such situations each user alwasy sees all changes.
Thanks