3.3.4

What's Changed

• adding logs including content for debug purposes (temporary files created will not be deleted on error for troubleshooting purposes)

3.3.3

This release contains the following changes:

1. Bump up the version of org.json:json to address a vulnerability (CVE-2022-45688)
2. Improve logging to identify which Cloud instance a user tried to connect to

3.3.2

This release corrects logging when the upload of Cucumber results to Jira instance fails

3.3.1

This release fixes a bug that prevented users from saving configurations if no servers were defined in Manage Jenkins -> Configure System.

3.3.0

Now Zephyr Scale is compatible with Jenkins Configuration as Code and you can use YAML file to automate your configuration process.

3.2.2

This release provides a layer of security against a Zip Slip vulnerability when unzipping zip files.

3.2.1

This release fixes incorrect handling and upload of Cucumber result files in Zephyr Scale plugin on Jenkins for Windows.

Allow customization of created test cycle when publishing test results to Zephyr Scale Server

When the plugin publishes test results to Zephyr Scale Server, it's now possible to set the test cycle name, the description, the folder, the project version, and custom fields.

Fix an issue when trying to publish test results without a custom test cycle

There was an issue that prevented users from publishing test results to Zephyr Scale if they didn't check the box to customize their test cycle.

Expand environment variables in custom test cycle

Fixes an issue where variables used in the custom test cycle fields were not being expanded.

You can use variables with the ${MY_VAR} syntax, just as you would do with any other Jenkins field, and you will see the variables' values in Zephyr Scale Cloud.