I am in the process of trying to implement version control software with studio. Has anyone got any recommendations (either Linux based/windows based) as a place to start I have installed Gitlab and I wanted to know whether anyone has come across any obstacles using this.
I was also wondering whether anyone has developed any hooks for Gitlab that works well with Studio as I would prefer if there was a more integrated solution with studio? Any help with this would be great.
I posted a question here about a week ago about GIT. I believe we understand it well enough to use. We are still trying to determine the best flow for our needs.
But now the question is how do we integrate this with GIT?
We are new to both Git and Atelier and would love to get advice.
Currently I believe the flow would be something like this:
1.Create a branch from our origin repository (let's say Ticket 123 branch)
2.Download that branch locally to our PCs with Cache running a local instance
Starting from the point that Eclipse uses local files on the workstation, COS development can be versioned with market tools (For example GIT or Subversion).
I would like to know how the community has worked with code versioning, to create a consistent versioning model.
I'm using Git with DeepSee and when I need to do a commit to the git repo I'm exporting ALL the pivots and dashboards from the namespace. But I can forget to do that) And it can take time for a large system.
What is the way to manage automatical export of DeepSee artefacts which we are editing in UI (Cubes, Pivots, Dashboards, Pivot Variables, Term lists, Shared Measures) into files every time when I push Save button?
I am using Atelier + EGit plugins for a project. Is it possible to turn the storage definition off in Atelier so this does not get copied to Git when I make changes? While developing on different versions of the code on different systems, it may cause conflicts and excess noise in the source control history
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.