Using git when sharing code between Ensemble and IRIS instances- Storage definition challenges
We have a few projects and some of these projects share code "libraries". Some of which are persistent classes that are used by multiple systems. All these are currently deployed on Ensemble. We want to move some of the smaller ones to the cloud and make use of IRIS.
The challenge is that once we synchronise the code to IRIS from Atelier, then IRIS changes the storage definitions, which then creates changes to the files. We do not want to commit all these changes to git as it will happen again once someone synchronises with Ensemble. The developers also need to be able to make changes to the classes, regardless of whether it is deployed to Ensemble or IRIS.
We can try and create multiple branches on git, but this will mean we will constantly have to merge code on every class that contains a storage definition. This creates too much overhead and wastes time.
Currently it seems like a bit of a deal breaker to migrate to IRIS. Some of the projects on Ensemble can't migrate to IRIS now as it is running on Solaris SPARC, which is not supported on IRIS.
Any thoughts on how we can still accomplish this goal without creating too much overhead?