Installing and configuring Git

This procedure describes how to install and configure Git in order to store all your project data, such as Jobs, Database connections, Routines, Joblets, data models, processes, or stored procedures, in the shared Repository of the Talend Studio.

For more information on the supported Git servers, see Compatible version control systems.

Note: This procedure might not be necessary if the Git server you install already provides Git and you do not need it on your local machine.

Procedure

Download the Git version corresponding to your system at https://git-scm.com/downloads and follow the installation instructions.
Create an SSH key pair.
1. Open a terminal instance.
2. Generate a new key by using the following command, where email is the email address of the Git server account:
```
ssh-keygen -t ecdsa -b 256 -m PEM -C "email"
```
3. When you are prompted to enter a file in which to save the key, press Enter to accept the default file location, or type a name and press Enter.
4. When you are prompted to enter a passphrase, press Enter to leave it empty.
Put the generated key file in the /home/User_Name/.ssh folder.
Add the public key to the settings of your Git server.
1. Create a known-hosts file by executing the following command:
  
  ssh-keyscan -H git_server_hostname >> known_hosts
2. If you are using multiple SSH private keys, create a config file in your .ssh folder and add the following content in the file to specify which key file is used for which Git server.
  
  Information noteWarning: This config file takes precedence over the Eclipse configuration.
```
Host <git_server1_hostname>
IdentityFile /home/username/.ssh/key1
Host <git_server2_hostname>
IdentityFile /home/username/.ssh/key2
```
Add the connection information to the Talend Administration Center configuration. For more information, see Setting up Git parameters in Talend Administration Center User Guide.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here