Has anyone tried versioning FME workspaces with a versioning software such as TFS?
If yes, how did it go? Did you experience any issue?
Thanks in advance,
Maryse
Dear all,
Page 1 / 1
We store all our workbenchs and ETL tools in TFS and have not seen any issues with. One thing we havent tested was merging changes between workbenches. I am curious if there are issues with that though (we just checkout and lock the file if we are going to edit it).
-Sean
Merging changes in workspaces would almost certainly end in disaster. Even tiny edits can drastically change the order of the contents.
We work like Sean and have seen no problems. You can compare the files between versions as text files but I'd be wary of merging so would treat them like binary objects, checkout and lock, no shared editing etc.
Rob
I am using GIT to version my workspaces. Since workspace files are basically text files, GIT works great!
-Carl
I just wanted to point out that I've been storing FMW files in Git for quite a while, but it is less than ideal because small changes in the workspace result in HUGE changes to the text file. The biggest offenders are item orders changing dozens or hundreds of lines, and each embedded custom transformer having its own unique ID that changes every time you save. I hope that this behavior can be improved in the future so that VCSs are more viable.
I guess the no risky way of managing workbenches in TFS would be that of CheckOut, Lock for updates and CheckIn.