Book a Demo

Author Topic: Version Control - Get All latest import files although model is up to date  (Read 5824 times)

Dieter Goetz

  • EA User
  • **
  • Posts: 43
  • Karma: +0/-1
    • View Profile
Hi all,

we are working with a server based EA-Project and packages under version control.
One user performs a get all latest. I would suppose the EA-Project is now up to date. But if another user performs get all latest on the same EA-Project and the same svn Repo EA starts to import XML files. We have the same behaviour for a file based EA-Project (EAP-file was for both users the same). The EA-Project is for bother users different after the get all latest.
It seems that EA find differences for an identical svn Repo. Do you have any ideas?

Best regards
Dieter

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
We do not share EA repositories under version control, so I do not have a concrete idea were the differences are coming from.
However I know when working with internal baselines, differences are shown e.g. in created or modified date an on diagram properties which should not be there. Here I assume that either importing or exporting is not really clean.
For SVN I do not have such differences but due to the fact that we do not share our ea DB’s I do not have your use case.
What I would try, is to compare the model with SVN content by “Compare With Controlled Version” for both users to get a feeling what causes the difference of the same.
Best regards,

Peter Heintz

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
If you use version control then you must NOT use a shared repository. This is, well, a bad idea. Either use VC with separate EAP's (or whatever) for single users. Or (preferred) use a shared repository with locking.

q.

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
I could imagine some very special use cases were version controlled repositories might be shared. But in general, yes you should not share.
However, the differences described should not be there anyway.
Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Hi Dieter,

Everyone has their own idea's about version control and shared repositories, but I've been using VC on shared repositories for years now without any issues.

But indeed, if you do a getAlllatest on a repository that is already up to date you will get that behavior. Not that it should matter (except that it takes a bit of time), because the files are the same, and so the end result should be the same.

I don't think there's much that anyone can do about that since EA can only know that your files are up to dat by asking your VCS, and since it was another use who did a getLatest, your VCS doesn't know about that.

Geert

Dieter Goetz

  • EA User
  • **
  • Posts: 43
  • Karma: +0/-1
    • View Profile
Hi Geert,

it is really a strange behaviour. First we thought that is because of different EAP-files and afterwards both EAP files are the same. We are not quite sure, but it seems to result in different EAP files.
With our EA-project get all latest runs in an error endless loop because of the database size.
Then we tested in a server based EA-repo. I expected after one user did get all latest EA will not import any xml file for the next get all latest - independent on the user.

We will do some additional testing.

Dieter