Shared repository multiple version control system?

[Paolo F Cantoni]

In a shared repository (such as SQL server) is it possible for different users to employ different version control mechanisms?
For example, Fred might use SVN while Dorothy uses GIT.

I don't want to say why at this time; as, if the answer to the above questions is no, then the reason why is moot.

TIA,
Paolo

[Geert Bellekens]

Sure, as long as you don't want to control a single package in both VCS I don't see why not.

Geert

PS. GIT is not a supported VCS

[qwerty]

PS. GIT is not a supported VCS

because it has conceptually no central locking mechanism which is needed to avoid (impossible) XML merging.

q.

[Paolo F Cantoni]

Sure, as long as you don't want to control a single package in both VCS I don't see why not.

Geert

PS. GIT is not a supported VCS

Thanks for the clarification, Geert.

Unfortunately, the scenario will (potentially) require the same package controlled by more than one VCS (but not by the same user on the same machine).  Can you (or anyone) confirm that's NOT possible?

So, assuming only one VCS, would it be possible to set up VC packages but have ONLY one machine/user save to the VC repository?
I understand I can have a VC package, but not install VCS on my machine and I can then have EA suppress the "You haven't set up your VCS!" messages.

TIA,
Paolo

[Geert Bellekens]

Hi Paolo,

That is indeed not possible. The version control configuration is stored on the package level, and you can only select one configuration per package.

The second scenarion is something we do all the time. We have some framework packages that are shared between repositories. Only the architects are allowed to edit them and check them in into VCS.

At this client the architects are the only one that have version control configured at their machine. All the other users don't. They had to tick the checkbox to avoid popups about incomplete configurations once (a checkbox that was made on my request because of this setup)

Geert

[Paolo F Cantoni]

Hi Paolo,

That is indeed not possible. The version control configuration is stored on the package level, and you can only select one configuration per package.

The second scenario is something we do all the time. We have some framework packages that are shared between repositories. Only the architects are allowed to edit them and check them in into VCS.

At this client the architects are the only one that have version control configured at their machine. All the other users don't. They had to tick the checkbox to avoid popups about incomplete configurations once (a checkbox that was made on my request because of this setup)

Geert

Cool!  Again, thanks Geert!  I was pretty sure the second scenario was working as you described but not definite!

Taking this scenario further, the VCS can figure out if a package branch changed and ONLY export an XMI if the package did actually change - yes?

Do you know what constitutes a change to a package to cause the VCS to emit the XMI?

Paolo

[Geert Bellekens]

Hi Paolo,

I think once you checkout a package EA will generate an xmi when checking in regardless of any actual changes.
And very probably there will always be minor changes in things like dates, order of elements etc...
So even if you checkout a package, don't change anything and check it in again there might be a difference in xmi file.

The version control checks are pretty rigorous. EA won't let you change anything if you haven't checked out the package. The are even a bit stricter then the checks when using security alone (apply user lock)

Geert

[Paolo F Cantoni]

Hi Paolo,

I think once you checkout a package EA will generate an xmi when checking in regardless of any actual changes.
And very probably there will always be minor changes in things like dates, order of elements etc...
So even if you checkout a package, don't change anything and check it in again there might be a difference in xmi file.

The version control checks are pretty rigorous. EA won't let you change anything if you haven't checked out the package. The are even a bit stricter then the checks when using security alone (apply user lock)

Geert

(my emphasis above...)
Could a Sparxian confirm this please?

Similar to the problem with processing the diagrams on each element, it takes so long to generate the XMIs that we need to become smarter about which XMIs to generate on our scan.

TIA,
Paolo