Hello,
We are using GIT as source control for our talend project. This lead to several limitation and you should using it only if svn is not an option for you.
Things you should keep in mind:
1. Because Talend make changes to the talend.project.xml file when you close the project, you can have only one developer working per project at the same time (if not you will face merge conflict to resolve manually)
2. You need to add and commit your full project each time (those loosing the power of git regarding commiting individual file)
3. Because of 1 and 2 you have to create a separate Talend job for each project and not a unique central project referencing all your jobs
4. the git diff is hard to read due to all behind the scene talend is doing
Here is the shell script we are using to initialize git in each talend workspace folder:
#!/bin/bash
git init
echo "
# generated everytime you open the project
/temp > .gitignore
/code/routines/system/ > .gitignore
/sqlPatterns" > .gitignore
git add .
git commit -m 'initial project version'
Some documentation I found on this topic
-
https://bowerstudios.com/node/871-
http://richardlog.com/post/15939924496/putting-talend-open-studio-projects-under-version-
http://blog.courtine.org/2011/03/26/partager-un-projet-talend-open-studio-avec-git/ (french)
-
http://datacatalyst.blogspot.ca/2012/06/version-control-talend-jobs-with-github.html
