Testing and applying a monthly update via a proxy server

When testing and applying a Talend Studio monthly update, it is recommended to use a proxy server, with Sonatype Nexus or JFrog Artifactory, to control the update applied via an administrator account and to apply it to several Talend Studio instances at once.

Workflow diagram of an administrator who receives a new monthly update. They start by validating the monthly, then set up the update on a proxy repository before deploying it to all Talend Studio instances used by developers.

Before you begin

Make sure Sonatype Nexus or JFrog Artifactory is installed and configured. In the following steps, <repo-server> refers to the IP address or host name of your Sonatype Nexus or JFrog Artifactory server.
All Talend Studio instances which share a project must be updated to the same version. Make sure you are aligned with your team about the version to use.
In the following steps, Studio_Prod refers to a production Talend Studio instance, and Studio_Test refers to a Talend Studio instance used for testing purpose.

About this task

Let's say, as an administrator, you want to test a monthly update on your Talend Studio and apply it to several Talend Studio instances.

Procedure

Create a proxy repository in a raw format with Sonatype Nexus or a virtual repository in a generic or maven format with JFrog Artifactory, used for validating the monthly update, and name the repository as repo-202204 for example.
Link the repository to the Talend Studio monthly update you want to test, https://update.talend.com/Studio/8/updates/R2022-04 for example.
If you are testing and applying the 8.0 R2022-04 Talend Studio monthly update or a later one provided by Qlik, do the following:
1. Install a new Talend Studio instance used for testing purpose, Studio_Test for example, and launch it.
2. In the Preferences > Update settings view, set up the update URL, http://<repo-server>/repo-202204 in this example.
  
  For more information about how to configure the update URL, see Configuring update repositories.
3. Click the Feature Manager button on the top bar, install the monthly update and restart Talend Studio.
4. Open the remote project on which you want to test migration.
  The Migrate projects or test wizard displays.
5. Select Test and click Next.
6. In the Branch name suffix field, enter the name suffix for your testing branch, and then click Finish.
  The testing branch is automatically created. Your project is migrated to the new version on the testing branch, and Talend Studio opens your project on the testing branch in the local mode.
  Note that if your project has any reference projects on other branches than the main project, Talend Studio creates test branches for them as well on a per branch basis. All reference projects are also migrated to the new version on the testing branches and the main project automatically references them on the testing branches.
7. Click the top bar of the Repository tree view and select Push from the drop-down menu to push the changes on the local testing branch to the remote end.
  Note that if your project has any reference projects, Talend Studio by default pushes only the main project. However, when testing project migration, Talend Studio pushes all testing branches for all main and reference projects in the first push after testing branches being created.
8. Validate your project on the testing branch, either in Talend Studio or using Continuous Integration.
If you are testing and applying the 8.0 R2022-03 Talend Studio monthly update or a previous one provided by Qlik, do the following:
1. In a production Talend Studio instance, Studio_Prod for example, create a testing branch based on the production branch, branch_test for example.
  Note that if your project has any reference projects, before testing the project migration in Studio_Test, you first need to create testing branches on a per branch basis for all main and reference projects in Studio_Prod, then open the main project on the testing branch in Studio_Prod and change its reference project settings by referencing each project on the testing branch.
  For more information, see Creating a new branch based on a selected source. You can also create a branch without Talend Studio using Git.
2. Install a new Talend Studio instance used for testing purpose, Studio_Test for example, and launch it.
3. In the Preferences > Update settings view, set up the update URL, http://<repo-server>/repo-202204 in this example.
  
  For more information about how to configure the update URL, see Configuring update repositories.
4. Click the Feature Manager button on the top bar, install the monthly update and restart Talend Studio.
5. Open the remote project on the testing branch, branch_test in this example.
  Note that if your project has any reference projects, all reference projects must be migrated before the main project.
6. In the dialog box displayed, click OK to migrate your project to the new version on the testing branch.
7. Validate your project on the testing branch, either in Talend Studio or using Continuous Integration.
If you have not created a production repository for Talend Studio monthly updates, create a group repository in a raw format with Sonatype Nexus or a virtual repository in a generic or maven format with JFrog Artifactory, and name the repository as repo-prod for example.
Link the production repository to the repository used for validating the monthly update, repo-202204 in this example.
For each Talend Studio instance you want to update, set up the update URL in the Preferences > Update settings view using the URL of the production repository if you have not done so, http://<repo-server>/repo-prod in this example.
Once the update URL is correctly configured, you can click the Feature Manager button on the top bar and install the monthly update.

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