Skip to main content Skip to complementary content

Configuring Jenkins

Installing Jenkins plugins

Add the additional plugins necessary to execute your pipelines in the Jenkins server.

  1. In Jenkins, navigate to Manage Jenkins > Plugins.
  2. Click the Available plugins tab to see the available plugins.
  3. Type in the following plugin names in the search bar and select them:
    • Blue Ocean (to visualize in details the Pipeline workflow)
    • Config File Provider (to add your customized maven settings file to Jenkins)
    • Docker
    • Git server
    • Maven Integration
    • Pipeline (set of tools for modeling scripted Continuous Deployment Pipelines in Jenkins)
    • Pipeline Maven Integration
  4. Click Install to install all plugins at once without restarting the Jenkins server.

Configuring paths to Git and Maven tools

Store the environment variables and paths to the third-party tools needed to run your Jenkins pipeline (Git, Maven).
  1. Navigate to Manage Jenkins > Tools.
  2. In the Git installations area, add the Git executable. Either enter the path to your Git executable file, or select the Install automatically check box if you want to install a new one automatically.
  3. In the Maven installations area, add the M3 Maven tool. Either enter the path to your Maven installation directory in the MAVEN_HOME field, or select the Install automatically check box if you want to install a new one automatically.
  4. Click Save to take the changes into account.

Storing your login credentials in Jenkins

Store the login credentials of your source control management tool and deployment containers (Docker, Amazon AWS, Azure, etc.) in Jenkins.
  1. Navigate to Manage Jenkins > Credentials.
  2. Click System > Global credentials > Add Credentials and add the Git credentials to access the repository where your project items (Jobs, Routes, Tests, etc.) are stored.

    If you are using Git personal access tokens, select Username with password. If you are using SSH, select SSH username with private key in the list.

  3. Name its ID git_talend, this identifier will be used in the Jenkins pipeline.
  4. Click Create to take the changes into account.

Storing your configuration files in Jenkins

  1. Download and extract these files:
  2. In Jenkins, navigate to Manage Jenkins > Managed files.
  3. Click Add a new Config and select Maven settings to add the Maven configuration file.
  4. Give it a name and an ID, maven_settings. This identifier will later be used in the Jenkins pipeline.
  5. In the Content editor, paste the content of the maven_settings.xml file you have previously downloaded.
    • The default Nexus artifactory URL defined in the file (line 40) is localhost:8080. Update the value according to your environment.

    • For Big Data users with dynamic distributions only: add the following server and repository to the configuration file in order to define the Nexus local repository as proxy, ensuring faster .jar file downloading:

      <server>
    <id>dynamic-distrib</id>
    <username>admin</username>
    <password>Talend123</password>
</server>
      <repository>
    <id>dynamic-distrib</id>
    <name>dynamic-distrib</name>
    <url>http://localhost:8081/repository/dynamic-distrib/</url>
    <layout>default</layout>
 </repository>

      For this configuration to be complete, you need to have previously added the Talend proxy in the Talend Studio Project settings > General > Dynamic Distribution Settings menu.

      For more information, see Adding the latest Big Data Platform dynamically.

  6. Click Submit.
  7. Click Add a new config and select Groovy file to add the Jenkins helper configuration file.
  8. Give it a name and an ID, jenkins_talend_helper. This identifier will later be used in the Jenkins Creating the Jenkins pipeline.
  9. In the Content editor, paste the content of the Groovy file and click Submit.
  10. Click Add a new config and select Custom file to add your Talend license file.
  11. Give it a name and an ID, license. This identifier will later be used in the Jenkins Creating the Jenkins pipeline.
  12. In the Content editor, paste the content of the license file and click Submit.

These files contain the connection information to your artifact repositories, the definition of the pipeline steps as well as the license information. These files will be are referenced in the configuration of your Jenkins pipeline.

Storing the CI Builder plugin in Nexus (deprecated)

The CI Builder plugin is necessary at build time, it is used to automatically download and install the P2-based Talend CommandLine as well as to generate the POM files of your project.

Information noteNote: The following procedure is optional for Talend CI Builder 8.0.4 and higher. Starting from Talend CI Builder 8.0.4, it is available in the official Talend repository, which is referenced in the maven_settings.zip file.
  1. Retrieve the CI Builder plugin archive, either from your license email, or from the Continuous Integration (CI) for cloud section of the Downloads page of your Talend Cloud account.
  2. Start your Nexus application log in your account.
  3. Create a repository named talend-custom-libs and upload external libraries in your Nexus repository.
  4. From the Nexus home page, click Browse on the left panel.
  5. Select the talend-custom-libs repository in the list.
  6. Click Upload on the left panel to upload the CI Builder files.
  7. In the Choose assets for this component area, browse to the following CI Builder files you have previously downloaded: builder-maven-plugin-8.0.x.jar and builder-maven-plugin-8.0.x.pom.
  8. Click Upload.

The CI Builder files are uploaded to your artifact repositories. The plugin will be used in the CI pipeline.

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