Book a Demo

Author Topic: Model Basline + Version Control  (Read 2745 times)

yiki

  • EA User
  • **
  • Posts: 39
  • Karma: +0/-0
    • View Profile
Model Basline + Version Control
« on: January 17, 2012, 07:04:51 am »
I wana take advantage of the built in "model baseline", at the same I wana use version control in a distibuted team using local models.
is this a good, and pouplar method? or what's the most efficient method to use?


I'm testing the process on my local machine.
I have put my packages under version control and created couple "baselines" and than made copies of the ".EA" file that i'm using.

I noticed that when accessing the copies of ".EA" the "baselines" are still there. However, whenI delete a pakcage I try to import it again the baseline disapear. I'm assuming that as long as the package is still in the ".EA" it pretain the model basline since the ".EA" is the database, and when you delete it and put it back again , the ".ea" file loose the related information of that package.


qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Model Basline + Version Control
« Reply #1 on: January 17, 2012, 07:42:54 pm »
The baseline is always local the the repository and not under VC. It's kind of two different variants of VC.

q.

yiki

  • EA User
  • **
  • Posts: 39
  • Karma: +0/-0
    • View Profile
Re: Model Basline + Version Control
« Reply #2 on: January 18, 2012, 03:11:12 am »
But if you use the same repository say ".EA" file even if you put your packages under VC , the baseline will be reserved. Except if deleted the package than imported again that's when you loose it right?