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
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, Talend 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
Results
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.