Using Git and Subversion in Talend Administration Center - 7.1

Irshad Burtally
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Administration and Monitoring > Managing projects
Administration and Monitoring > Managing versions
Talend Administration Center

Using Git and Subversion in Talend Administration Center

This article shows how to use Git and Subversion in Talend Administration Center.

Talend uses either Git or Subversion as a repository for storing job designs and artefacts that developers and designers create with the Talend Studio. Talend has been using Subversion as a repository since version 4.x. Git support was introduced in Talend 6.1.1. Both Subversion (SVN) and Git are supported in the subscription version of the products.

Can I use both Git and Subversion within the same Talend Administration Center?

You can configure both SVN and Git at the same time in the Talend Administration Center Configuration Menu as shown in the screenshot below. Both configurations are optional since Talend Administration Center can also have projects of type None for storage. The screenshot below shows both Subversion and Git pointing to a repository. Please note that Subversion repositories are slightly different from Git repositories in the way projects are managed and branched/tagged.

Configuring Git or Subversion in Talend Administration Center

This section explains how to configure Git or SVN in Talend Administration Center.

It is recommended to choose either Subversion or Git and to stay with one system to make it easy for your development team.


  1. Set the storage setting. Talend Administration Center allows you to choose between SVN, Git or None, as shown in the screenshot below.

    The screenshot below shows 3 projects with a different storage type.

    A storage setting of None means that there is no actual object or project stored in any SCM. The project is just a label or placeholder for managing rights and permissions for users. The authorizations can be set through the Project Authorizations and Server Project Authorizations pages.

  2. Make sure that the users you have created in Talend Administration Center have either their SVN or Git login details captured, as shown below.


Once you have set the parameters for Git or SVN, you can connect to the remote project in the Talend Studio. The UI is mostly the same, the difference is only on the General tab of the Job where instead of SVN History, you see Git History, as shown below. Talend Studio also uses the terminology of the SCM everywhere appropriately, i.e. trunk for SVN and master for Git.

In summary, Talend makes it easy to use both Subversion and Git. The main differences are in the way the two SCM behave and the workflow needed when using them.