Book a Demo

Author Topic: version control - "get all" ?  (Read 3861 times)

gpc

  • EA User
  • **
  • Posts: 111
  • Karma: +0/-0
    • View Profile
version control - "get all" ?
« on: October 24, 2007, 05:56:45 am »
Why is the Get all / latest functionality a feature of whether the source is shared or private?
I'm working on a collaborative project and the packages contain a number of sub-packages, all of which are under version control. when creating a project from scratch I need to pull in the top level package, change my vc setting to private, then get all. After that I set my vc to shared and can continue.
so not a problem, but just can't think of why one is affected by the other?

thomaskilian

  • Guest
Re: version control - "get all" ?
« Reply #1 on: October 24, 2007, 07:13:04 am »
Sparx explained it, but honestly I also don't understand why they do it their way ???

I'd rather like to check out my sources via Tortoise, load once into EA, export eventually and then submit in one bunch via Tortoise. Don't like that built-in VC handling. Really clumsy and un-intuitive.
« Last Edit: October 24, 2007, 07:16:08 am by thomaskilian »

gpc

  • EA User
  • **
  • Posts: 111
  • Karma: +0/-0
    • View Profile
Re: version control - "get all" ?
« Reply #2 on: October 24, 2007, 07:26:42 am »
but with the "get all" command, you'll have to search for all vc packages and perform a 'checkout' + 'undo checkout' for each package? crazy!  :P

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: version control - "get all" ?
« Reply #3 on: October 24, 2007, 01:05:44 pm »
It's disabled for shared models because another user could be working on a package in the same model.  Get the latest from version control an import it and they lose their work.

So it's blocked to prevent that dangerous situation.

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: version control - "get all" ?
« Reply #4 on: October 24, 2007, 11:01:58 pm »
As I understand it, during the "Get All Latest" command packages are not locked in local CVS Working copy.

Suggestion:
What about to implement "Get All Latest" in shared projects in such way, that it will lock packages while importing them and skip packages, that it's not able to lock (these packages are check outed by another user).
Peter

gpc

  • EA User
  • **
  • Posts: 111
  • Karma: +0/-0
    • View Profile
Re: version control - "get all" ?
« Reply #5 on: October 25, 2007, 12:33:33 am »
I'm using perforce and we have to manually lock the checked-out file - this doesn't happen as part of the check-out procedure (shared or private) - I'll probably need to script something at some point.
Re comment: If another user is working on a checked out version, then I select get all - this gives me the latest from the vc store. This only affects the other users work if I check out and make changes then check in.
The conflicts only arise on check in and should have nothing to do with check-out / resync / get latest?