Best practice: Testing a Talend Studio patch

Before installing a patch to fix an issue or migrate to a newer version of Talend Studio, it is recommended to test the patch on your existing Jobs or projects.

Using Continuous Integration to test an update before applying it to Talend Studio

Use specific Maven commands to test an update on one or more projects before applying the update to Talend Studio.

Procedure

Check out your Git projects.

Download the update from the Talend update site URL you have set up using the -Dtalend.studio.p2.update Maven parameter.

Example:

-Dlicense.path=/home/talend/talend_studio/license
-Dtalend.studio.p2.base==https://update.talend.com/Studio/8/base
-Dtalend.studio.p2.update=https://update.talend.com/Studio/8/updates/R2022-01

Re-generate all the POM files of the project workspace and install the updates you want to test.
For more information on how to re-generate all POM files, see Generating POM files for your projects.
Test the generation of existing projects and Jobs.
If the project generation is successful, apply the tested updates to Talend Studio. If the test is not successful, contact Qlik Support.

Downloading a patch

Before you begin

All the Talend Studio instances which share a project must be updated to the same version. Ensure to align with your team about the version to use.

Procedure

Depending on the version of the patch you need to download, do the following:

If you need to download the latest monthly update, download the patch directly from the Downloads page of your Talend Cloud portal.
If you need early access to a new patch, or to download an older patch, ask Qlik Support to assign the patch to your customer account. Qlik Support will also create a Talend Remote Nexus server account on your behalf to host the patch. Once receiving the reply, in Talend Remote Nexus server, sign in with your client credentials and go to the exact URL provided by Qlik Support to download the patch.

Applying and testing a patch in Talend Studio

About this task

Before applying the patch on a Talend Studio production branch, Qlik recommends to first create and use a test branch for the patch testing.

In the following steps:

Studio_1 refers to the current Talend Studio instance used for production.
Studio_2 refers to the Talend Studio instance used for testing the patch.

Procedure

Open your current Talend Studio instance and select the project you want to test the patch on.
Create a new branch named patch_testing (or any other name) based on the production branch. For more information on the creation of branch with Talend Studio, see Creating a new branch based on a selected source. You can also create a branch without Talend Studio using Git.
Install another Talend Studio instance (Studio_2) to test the patch.
Apply the patch in the Studio_2 instance manually and launch it. For more information, see Applying a patch to Talend Studio.
Select the project in the patch_testing branch.

Information noteWarning: If the project has reference projects, you need to log into the main project with the first Talend Studio instance (Studio_1) to change the project reference to your test branch (in this example, patch_testing) to make sure all the projects you test are on the patch_testing branch. Then, use the Studio_2 to migrate the reference projects before the main project.
A warning window appears, click OK to migrate the project to the new patch version.

Results

You applied the patch to Studio_2 and migrated your projects in the patch_testing branch. You can now test the patch.

If the test is successful, you can apply the patch to the Talend Studio instance used for production (Studio_1) and migrate other production branches.

If the test is not successful, contact Qlik Support.

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