Skip to main content

Continuous Integration: new features

Feature

Description

Available in
Talend CommandLine installation Talend Studio now provides two scripts, commandline_upgrade.bat for windows and commandline-linux_upgrade.sh for Linux, which allows you to install Talend CommandLine by upgrading either a brand new or an existing Talend Studio.

All subscription-based Talend products with Talend Studio
Updates of CI Maven parameters related to patch installation Some CI paremeters used to install Talend Studio patches and updates have been changed:
  • -Dupdatesite.path parameter is now replaced with 2 parameters: -Dtalend.studio.p2.base is used to define the URL where the Talend Studio P2 repository is located, and -Dtalend.studio.p2.update is used to define the URL where cumulative patches are stored.
  • -Dpatch.path parameter can still be used but only for archive documents or component patches, for cumulative patches you need to use the -Dtalend.studio.p2.update parameter.

All subscription-based Talend products with Talend Studio
Updates of CI Maven parameters related to Docker Some CI parameters used to publish artifacts to Docker have been changed:
  • -Ddocker.push.registry parameter is now replaced with -Djkube.docker.push.registry.
  • -Ddocker.push.username parameter is now replaced with -Djkube.docker.username.
  • -Ddocker.push.password parameter is now replaced with -Djkube.docker.password.
  • -Ddocker.host parameter is now replaced with -Djkube.docker.host.

All subscription-based Talend products with Talend Studio
Project POM files not committed by default From version 8 onwards and for performance reasons, the POM files of your project are not committed by default in the Git repository but can be easily generated and updated when necessary.

To generate all POM files of your project, execute the mvn org.talend.ci:builder-maven-plugin:8.0.1:generateAllPoms command at build time.

All subscription-based Talend products with Talend Studio

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