Version Control Settings Problem

[SimonDMU]

When attempting to configure the version control settings I perform the following:

Install and create Tortoise svn repository.
(in EA) Project (menu) > Version Control > Version Control Settings
Create the Unique ID
select type "subversion"
Select the bath for storing the working copy (as per video demonstration)

The problem occurs when adding the 'Workstation settings' I press the "select path..." button and navigate through the directory structure to "C:\Program Files\TortoiseSVN\bin" BUT there is no svn.exe to select...it doesn't exist in that location, or any other location.

Has anyone got any suggestions as to what is missing?
Is there a compatibility issue with Tortoise SVN and EA?
is the exe stored in a separate location i was unaware of?

[lubos]

In our environment we have installed both TortoiseSVN and svn package.
But I'm not sure if it is necessary...

[SimonDMU]

I have just read that:

"EA cannot use Tortoise to communicate with the subversion server it must your the subversion command line client"


this is taken from:
http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/tortoisesvn.html

What I find is not helpful is a suggestion or example of a way around this, What subversion command line client should be used with tortoisesvn, and for that matter I am not sure I know what a Subversion Command Line Client is. Mor advice woulbe be useful thanks!

[Geert Bellekens]

Simon,

Look here for more information.
IIRC the one from collabnet works fine with EA.

Geert

[SimonDMU]

Simon,

Look here for more information.
IIRC the one from collabnet works fine with EA.

Geert

Hi Geert,

Thanks for the advice, used collaborate and has enabled the svn function but now when attempting version control with our SQL repository we find that if a model is checked out by user A then checked in again it still seems to be locked by that user and nobody else can check a copy in or out. Have you experienced issues of models remaining locked even when checked back in?

We are planning to deploy this in our ICT department with 50+ members of staff who could potentially be accessing these models at some stage in the life cycle and this manner is too manual to be accepted across the organization.

Cheerio

Simon

[lubos]

Hello,

to clarify such strange situations it's usually usefull to check the staus of the corresponding XML file in SVN and the status of corresponding package in repository (table t_package column packageflags -- filter it by ea_guid of the package).

Try to write this info back to this thread...

[Geert Bellekens]

Also, make sure you read (and follow) the documents
http://www.sparxsystems.com/downloads/whitepapers/EA_Deployment.pdf
and
http://www.sparxsystems.com/WhitePapers/Version_Control.pdf

Geert

[SimonDMU]

Hello,

to clarify such strange situations it's usually usefull to check the staus of the corresponding XML file in SVN and the status of corresponding package in repository (table t_package column packageflags -- filter it by ea_guid of the package).

Try to write this info back to this thread...

Hi,

I performed as asked:

Both packages (as is a simple test model) have the following Package flags:

isModel=1;VICON=5;AN=1;Recurse=0;VCCFG=SVN_Test;CheckedOutTo=robis901;

isModel=1;VICON=5;AN=1;CRC=a4622bfe;Recurse=1;

The status of the XML file in SVN (local) is (and I am assuming you mean the same PackageFlags in the XML):

isModel=1;VICON=5;AN=1;Recurse=0;VCCFG=SVN_Test;CheckedOutTo=robis901;CRC=0;

and the version in the SVN server:

isModel=1;VICON=5;AN=1;Recurse=0;VCCFG=SVN_Test;CheckedOutTo=robis901;CRC=0;

I do not understand why this is a problem, and also I don not understand why each user will have their own copy in the repository. If UserA created a folder location in the svn server linked to a directory on their local machine, UserB cannot use the same svn server folder to check out the same packed after UserA has checked it back in becuase the XML file for that package already exists.

I'm not fully understanding how the version control function operates for EA as it seems to require a new file per person per checkout/in therefore replicating data stored in the rpository rather than overwriting the previous ones. Have I understood this correctly?

[Geert Bellekens]

Simon,

I think the idea is that each user has a local working folder on his machine where the checkedout files end up.

And I think lubos was trying to say to share the SVN status of the xmi file as well, just to see if there is a difference to status in EA and the status according to SVN.

Geert

PS. Please note that EA uses Exclusive locks only.