View Xray - Test Management for Jira on the plugin site for more information.
Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:
This plugin enables continuous integration using Jenkins and Xray Test Management. In a nutshell, this connector provides tasks to publish test results from Jenkins to Xray.
The documentation below it's a "Quick Start" version of our full documentation available in Xray official page:
- Xray Cloud: https://confluence.xpand-it.com/display/XRAYCLOUD/Using+the+Xray+plugin+-+Jenkins
- Xray Server: https://confluence.xpand-it.com/display/public/XRAY/Integration+with+Jenkins
You can also check the source code of the plugin here: https://github.com/jenkinsci/xray-connector-plugin
Upgrading from version below 2.1
If you are upgrading from a version below 2.1, you have to:
- Uninstall the old version of the plugin (xray-for-jira-connector)
- Go to the Xray configuration section and re-write your instances credentials
- Re-save (you don't need to change any data) any Project/Job that is using Xray steps.
- Integration with both Xray in Jira Cloud and Jira Server/Data Center
- Export Cucumber features files from Xray
- Import Cucumber feature files to Xray
- Import your test results in any format supported by Xray
- Jenkins 2.60.3 or above
- At least one Jira instance (Server, Data Center and/or Cloud) with the Xray installed.
If you need any help using in Xray Test Management for Jira or this plugin, you can contact by using our Support System.
Xray for Jenkins is configured in the global settings configuration page Manage Jenkins > Configure System > Xray configuration.
To add a new Jira instance connection, you need to specify some properties:
- Configuration alias: the name you want to give to this configuration
- Hosting: Hosting (instance type) in this case Cloud/Server/Data Center
- (Server/Data Center only) Server Address: The address of the Jira Server where Xray is running
- Use the Jenkins Credentials Plugin to set the username/password (if you are using a Server/Data Center instance) or an API key/secret (if you are using an Cloud instance)
- Make sure that the user you are using have the following permissions in the projects where you want to import the results and import/export feature files: View, Edit, Create
Note: the Configuration ID is not editable. This value can be used in the pipelines scripts.
After setting the instances, you can test your connection to Jira, by using the and Test Connection button.
When you are done configuring your Jira instances, don't forget to Save the changes.
Currently, we support Freestyle, Pipeline, Multi-configuration Projects and Maven projects.
This plugin provides 2 new Build tasks:
The Xray: Cucumber Features Export Task and the Xray: Cucumber Features Import Task
Both tasks can be used while executing Cucumber tests: In a typical Cucumber Workflow, after having created a Cucumber project and the Cucumber tests specified in Jira, you may want to have a project that exports the features from Jira, executes the automated tests on a CI environment and then imports back its results.
For this scenario, the Jenkins project would be configured with a set of tasks responsible for:
- Pulling the Cucumber project
- Exporting Cucumber features from Jira to your Cucumber project
- Executing the tests in the CI environment
- Importing the execution results back to Jira
In the Post-build Actions, you can add the Xray: Results Import Task, in order to import your Test Results in the following formats:
- Xray JSON
- Xray JSON Multipart
- Cucumber JSON
- Cucumber JSON Multipart
- Behave JSON (Xray Server/Data Center Only)
- Behave JSON Multipart (Xray Server/Data Center Only)
- JUnit XML
- JUnit XML Multipart
- Nunit XML
- NUnit XML Multipart
- Robot XML
- Robot XML Multipart
- TestNG XML
- TestNG XML Multipart
- xUnit XML (Xray Cloud only)
- xUnit XML Multipart (Xray Cloud only)