Sparx Systems Forum

Pro Cloud Server / Prolaborate / WebEA => PCS General Board => Topic started by: gbolton on December 31, 2020, 05:58:56 am

Title: Using Devops to move models between PCS environments
Post by: gbolton on December 31, 2020, 05:58:56 am

We have 2 Procloud environments.  Our current process is we export an XMI for the model from our test environment and import it into a production environment.  We also capture it in Github.  The model is so big (about 5000 elements) that I have to do multiple  exports and imports to synch the two up.  Has anyone implemented devops capabilities to handle the migration between Procloud repositories?  Any suggestions or lessons learned? 

Title: Re: Using Devops to move models between PCS environments
Post by: Geert Bellekens on December 31, 2020, 04:56:46 pm

If you want to move the whole model to your production environment then a simple backup/restore on the database level should do.
That is usually a process that takes less than 10 minutes.

If it's only a part of the model, you better look into integrating with version control.
Make sure to control the smallest units possible (e.g. every single package becomes a separate xmi file)

We have such a setup using an Azure Devops TFS repository. (you can't use Github as it doesn't support exclusive locks)

Another alternative is Reusable Assets.

Geert

Title: Re: Using Devops to move models between PCS environments
Post by: Guillaume on January 05, 2021, 03:06:42 am

Another option is to use the Native XML Project Transfer export/import.
I don't think this is yet available via EA API so it involves user actions via EA.
It generates XML files for each EA table that can be copied to your production server and lets you run the import.