Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Talend project in SVN

I need to use Talend Open Studio with a SVN. What is the folder that I should put in the repository?

like image 894
JMira Avatar asked Jan 05 '11 13:01

JMira


People also ask

Is SVN better than Git?

SVN is better than Git for architecture performance, binary files, and usability. And it may be better for access control and auditability, based on your needs.

How would you explain Talend project?

Talend is an open source software platform which offers data integration and data management solutions. Talend specializes in the big data integration. This tool provides features like cloud, big data, enterprise application integration, data quality, and master data management.


2 Answers

Well, the "official" answer is to upgrade to Talend Integration Suite (TIS), which includes SVN integration. It goes a long way to synchronizing the activities of several developers using a shared repository.

If TIS is not an option for you, you might have some success by putting the project directory of your Talend Open Studio (TOS) under SVN control. This is the directory immediately under "workspace" that has the same name as your project. You would have to perform all SVN operations, such as commit and update, manually on this directory, for example using Tortoise (if you're on Windows). TOS might be able to use this project as if it was not under SVN. I personally haven't tried this, and would recommend using TIS instead.

like image 103
drmirror Avatar answered Oct 17 '22 16:10

drmirror


Putting a TOS workspace under SVN is strongly discouraged, as CSV/SVN as file-based by nature while TOS workspace is directory-based. The probability that you incur in workspace corruption are very high.

However I achieved good results putting in under git, instead (have a look here for an idea). I must say it's not elegant and putting the entire workspace under version control is a tremendous waste of space (you will commit compiled files, logs, history, temp...), but it's the only safe solution for your metadata integrity.

Be aware! In *<workspace_root>/.java* subtree there are external libraries and the classpath files for each job in your project you executed at least one time. These paths are absolute. This mean that if you plan to use your version-controlled workspace in a shared environment anyone in team must place the workspace in the absolute location in their local file system (ie. c:/talend_git/workspace). Otherwise you'll get a class not found exception upon executing jobs. Sad but true.

like image 35
Gabriele B Avatar answered Oct 17 '22 18:10

Gabriele B