Book a Demo

Author Topic: Best Practice to Merge Model  (Read 2837 times)

Hardy

  • EA User
  • **
  • Posts: 45
  • Karma: +0/-0
    • View Profile
Best Practice to Merge Model
« on: August 15, 2012, 04:36:40 am »
Hi all,

We currently have main modelling done in EA, with every new project we add new stuff or modify existing models in EA. However, occasionally we need to cancel projects, in this case we have to reverse the changes done.

It is very common there are several projects running at same time, so reversing is not that easy.

Is there a best practice how to branch the model and merge after project is confirmed?

Thanks for any suggestion!

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Best Practice to Merge Model
« Reply #1 on: August 15, 2012, 12:06:10 pm »
Two methods you can use:
Simplest method is just create the baseline and revert back to it if the project is cancelled.
Alternative:
With Baseline merge, you can first copy a repository as a 'Branch', but also create a baseline of the Package-Tree for the Project that will be updated, in the source repository. The branch Package-tree can then be updated and if a merge is justified you use the Baseline Merge function "Load other Baselines" to merge back the Branch package tree from the Branch repository to the Source repository.