Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Boron on October 02, 2013, 06:00:55 pm

Title: Version control and automation interface
Post by: Boron on October 02, 2013, 06:00:55 pm
Hello,

I am looking for information concerning version control (package control) in EA and the automation interface.

My search in the EA help didn't answer the question if version control of packages is accessible via the automation interfaces or not.

I would like to run a "Get all latest" on an eap file called from a python script that uses the EA automation script.
Used EA version is 9.3.
Title: Re: Version control and automation interface
Post by: Geert Bellekens on October 02, 2013, 06:19:06 pm
Check the package class.
There's all kinds of version control operations that you can do from there.

Geert
Title: Re: Version control and automation interface
Post by: Aaron B on October 03, 2013, 09:22:16 am
Unfortunately there is no equivalent to the "Get All Latest" command via the automation interface at this time.
Title: Re: Version control and automation interface
Post by: Guillaume on November 14, 2013, 02:08:08 am
Could the Package Control Get All Latest method be added to the Repository class to avoid having to iterate through each package and run a GetLatest?
The workaround using Package.VersionControlGetLatest method will take ages to run I guess

Thanks
Title: Re: Version control and automation interface
Post by: qwerty on November 14, 2013, 03:51:42 am
Likely the GetAllLatest will do nothing else than iterate. So you have the choice: ages or aeons.

q.
Title: Re: Version control and automation interface
Post by: Eve on November 14, 2013, 08:07:41 am
While I agree that GetAllLatest in the automation interface would be nice, I would recommend writing a function to loop over the packages. There is the overhead of loading each package, that could be large with lots of packages in the model, but otherwise it's not going to be substantially slower than what Sparx would implement.

However, if you write a function for yourself you have it in the time it takes to write (and test) it. Otherwise you'll be waiting for us to put out a new build. You can always switch to our implementation when a build is released with the function available.