Book a Demo

Author Topic: Using Subversion  (Read 3055 times)

Heri

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Using Subversion
« on: March 20, 2007, 07:58:22 am »
Hello!!

Somebody have documentation about integrate EA and subversion? How works it?

Thanks

Oliver Michalski

  • EA User
  • **
  • Posts: 116
  • Karma: +0/-0
    • View Profile

GadgetGeek

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Using Subversion
« Reply #2 on: July 13, 2007, 05:37:33 am »
OK - still confused!

The .EAP file is controlled by subversion (and has the needs lock property set on it).

If I set up subversion control within EA to use the copy of the .EAP in my working directory, can others still work on the file (if in a different package within the model)?

Do I need to remove the 'needs lock' from the repositry first? If so, what then happens if someone opens the .EAP file from their working directory without having subversion configured within their copy of EA, and they then edit the file and commit changes??

Confused?
(Space, its big and dark - I like that...)

thomaskilian

  • Guest
Re: Using Subversion
« Reply #3 on: July 13, 2007, 12:46:18 pm »
Once I tried setting up SVN I got a warning each time I started EA without network connection. Annoying that was - reverted to complety checkin of EAP files (my server has lots of space).

bknoth2

  • EA User
  • **
  • Posts: 129
  • Karma: +2/-0
    • View Profile
Re: Using Subversion
« Reply #4 on: July 18, 2007, 01:12:04 pm »
I'm using EA with Subversion. If you remove the lock requirement for the .EAP file, my guess is that the person who commits the file second will overwrite all changes made by the person who checks in the file in before.

I have about five people working with a model through shared packages. We use MySQL and ODBC to hold the model (instead of a .EAP file, but a .EAP file will work the same way) and the packages are controlled through Subversion.

Subversion serves two purposes. One is that it provides access-control to the packages, keeping all users except one locked out. Secondly, it maintains a history of changes in each package.

I can give more insights if you have questions.

- Bruce