Specific migration from 2.0.0 to 2.1.1¶
Before migrating jobs¶
Updating Jenkins users¶
Due to security updates on Jenkins LTS 2.107 and 2.138 your users will have to be updated prior to starting the 2.1.1 version of Squash TF Execution Server.
- Delete the users directory from {new_server_path}/execution_home/
- Copy the users directory from {current_server_path}/execution_home/ to {new_server_path}/execution_home/ (keep a backup copy somewhere)
- Check that there is NO users.xml file at the root of the new users directory. It will automatically be created later.
The users’ updating process should automatically be done by Jenkins at the first start of the server, later in the generic process. You can comme back at this time to ensure the users’ update was successful :
- All the users are visible on the people page on Jenkins.
- A users.xml file should appear in the users directory of your new Squash TF Execution Server with the list of all your users.
- Each directory corresponding to a user should have a number following the user’s name.
For more details about this process visit the Jenkins upgrade guide for versions 2.107 and 2.138
Warning
This auto update is entirely managed by Jenkins. If you encounter any problem with your users (missing entries, bad API token or credentials…) we recommend retrying the process by stopping the server and doing steps 1 to 3 of this guide again.
Note
You could also recreate all the users from scratch. To do so, keep the users directory provided in a new install of the Squash TF Execution Server 2.1.1 instead of deleting it at step 2. Start the server to connect to Jenkins with the default administrator account (login : admin // password : admin) and recreate all your users from there.
Go back to the generic update procedure for now.
After migrating jobs¶
Verify users update¶
Prerequisites : You have followed the earlier instructions (in the Before migrating jobs section) to update Jenkins users.
Start your Squash TF Execution Server 2.1.1 and connect to Jenkins as administrator.
Go to Manage Jenkins
then to Manage Users
and check that all your users appear in the list :
If some of your users are missing you should stop the server, delete the users directory in execution_home (v 2.1.1) and copy again the old user directory (v 2.0.0) in its place (See **Before migrating jobs**).
Go back to Manage Jenkins
then to Configure Global Security
:
Check the authorization strategy used and verify the rights of each user in case of a matrix-based strategy.
If there is an error at this point you should retrieve a backup version of the 2.0.0 version of execution_home ( {old_server_path}/execution_home ) and copy the config.xml file to {new_server_path}/execution_home/.
(This config file is where the Jenkins authorization strategy is recorded).
Use an environment variable to define the maven local repository path¶
Overview¶
Previously, the local maven repository path was hardcoded by the installer during the installation process.
Starting from version 2.1.1 this path is define by using an environment variable. This change is not take into account by the generic migration and you have to do it yourself after.
Update the Maven Global Settings¶
Prerequisites : The generic migration should have been done.
Start your Squash TF Execution Server 2.1.1 and connect to Jenkins as administrator.
Go to Manage Jenkins
then to Config File Management
:
Open the file TF_MavenGlobalSettings and find the property <localRepository>.
Replace the line by :
<localRepository>${env.SQUASH_TA_HOME}/repository</localRepository>
and submit the changes.
Repeat this procedure for the file TF_Runners_MavenGlobalSettings.xml and submit again.
New reports publication settings¶
Overview¶
The jobs template settings for the reports publication have changed in Squash TF Execution Server 2.1.1. This change is due to a problem in the report publication url in Jenkins which was breaking the TM-TF link
This change have been made to all the templates.
Already existing jobs will have to be updated manually.
Note
These new reports publication settings are mandatory in case of a TF-TM link configuration and highly recommended in other cases.
Update existing jobs¶
In your job, go to Post-build Actions
:
- Replace all the spaces in the
Report title
fields for each report generated by the job.- Click on
Publishing options
under each report form.- The checkbox
Escape underscores in Report Title
now needs to be unchecked.
Final step¶
When all the procedures have been done you should restart your Execution Server, then reconnect to Jenkins and check that all the corrections have been successfully implemented.