Skip to main content Skip to complementary content

Installing and configuring Git

This procedure describes how to install and configure Git in order to store all your project data (Jobs, Database connections, Routines, Joblets, etc.) in the shared Repository of Talend Studio.

Before you begin

  • If your GitHub repository is hosted in a Microsoft Azure DevOps project, make sure the repository name doesn't contain spaces.
  • This procedure might not be necessary if the Git server you install already provides Git and you don't need it on your local machine.

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

Procedure

  1. Download the Git version corresponding to your system at https://git-scm.com/downloads and follow the installation instructions.
  2. Create an SSH key pair.
    1. Open the Git Bash.
    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.
  3. Put the generated key file in the C:\Users\User_Name\.ssh directory.
  4. Add the public key to the settings of your Git server.
    1. Create a known-hosts file by executing the following command:
      ssh-keyscan.exe -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. 
      Host <git_server1_hostname>
IdentityFile C:/users/username/.ssh/key1
Host <git_server2_hostname>
IdentityFile C:/users/username/.ssh/key2

What to do next

When creating a project in Talend Management Console, provide the connection information as explained in Creating projects.

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