Specific migration from 2.1.1 to 2.2.0


Before migrating jobs

No particular task needs to be done at this point for this update. Go back to the generic update procedure for now.



After migrating jobs


New reports publication settings

Overview

Since Squash TF Execution Server 2.2.0, we have changed our jobs template settings for the reports publication. Now the publication is done according to the operation executed :

  • If it’s a “list” operation, then we publish the tests list report.
  • If it’s a “run” operation, then we publish the tests execution report.

The change have been made to these templates :

  • 00Squash-TA_Template.
  • 00Squash-TF-Java_JUnit_Runner_Template.

Already existing jobs will have to be updated manually

Note

This new reports publication settings is mandatory for tests projects using :

  • Squash TFJava Junit Runner  : all versions.
  • Squash TFKeyword framework (SKF)  : for version 1.13.0 and above.

Update existing jobs

Prerequisite

The Flexible publish plugin should have been installed in Jenkins (done in Squash TF Execution Server 2.2.0).

In your job, go to Post-build Actions and add a post-build action :

Updating your existing Jenkins' jobs.

Select Flexible publish :

Updating your existing Jenkins' jobs.

Configure the conditional action for the goal list as shown in the screen below :

Updating your existing Jenkins' jobs.

Then add another conditional action and do the same for the goal run :

Updating your existing Jenkins' jobs.

For jobs which run tests using Squash TFJava Junit Runner, also add the “Squash_TF_HTML_Debug_Report” in the goal run  :

Updating your existing Jenkins' jobs.

Finally delete all previous post build actions for publication.

Note

As explain in the specific update documentation from 2.0.0 to 2.1.1, the report title should contain “_” (and not a space), and Escape underscores in Report Title should be unchecked.



Rename job execution according to the executed operation

Overview

In Squash TF Execution Server 2.2.0, we introduce the renaming of a job execution (according to the executed operation). To do so, we use the Jenkins Build Name and Description Setter plugin. This plugin sets the display name of a build to something other than #1, #2, #3, … so that you can use an identifier that makes more sense in your context (see image).

Updating your existing Jenkins' jobs.

Update existing jobs

Prerequisite

The Build Name and Description Setter plugin should have been installed in Jenkins (done in Squash TF Execution Server 2.2.0).

In your job, go the Build Environment section and check the box Set Build Name.

In the Build Name, just add :

#${BUILD_NUMBER}-${operation}
Updating your existing Jenkins' jobs.