May I ask if anyone has integrated version control using Git with Cube scripts?
Thanks in advance.
Hi, I've been using Cube Voyager with version control, first with SVN and then Git. I presented my experience using SVN at Futura 2011 (Futura 2011 Presentation Olav K Malmin.zip (1.8 MB)).
Using Git with Cube Voyager works pretty well and has been a lifesaver in the event of the APP-file getting corrupted. I also use branching and my repository is connected to a Jira Issue Tracker which is quite useful in a big project.
I would strongly recommend using SVN og Git when working with Cube Voyager. I would go so far as saying not using it is hight irresponsible.
There are some challenges to aware of:
- All files (APP, S) contains full file paths. If several developers are working with the same model, everyone need to be on the same path structure.
- The APP files are updated by Cube if something is changed in the model. If you link new files that is understandable, but sometimes many APP files are updated just with a new date and no new content. This is by Git recognized as a change in the file, so you must use caution when commiting new changes.
- Merging two branches can often lead to conflicts because of the APP files. You do not want to work on the same application in two different branches and then merge them. Git is usually not able to handle merging application files where both contain changes. Also if you have commited a APP file with just a new date this will also lead to a conflict
- The binary CAT-file is bit difficult to handle, but works OK if you do not change it between branches.