Xray for Jira Integration — CI Test Results to Xray

Automatically export Jenkins, GitHub Actions, and GitLab CI test results to Xray for Jira. Map CI jobs to Xray test plans, test executions, and test cases with a single BuildButler configuration.

If your team uses Xray for Jira to manage test cases, BuildButler can automatically sync your CI test results into Xray test executions. One JSON configuration covers all your CI systems — Jenkins, GitHub Actions, GitLab CI, TeamCity, and BuildKite.

How it works

BuildButler maps CI test results to Xray test cases, test executions, and test plans within your Jira project. After each build, results are exported automatically based on your configuration rules.

Already using the Xray Jenkins plugin?

Xray provides its own Jenkins plugin for importing test results. It works well — but it's Jenkins-only. If your team also uses GitHub Actions, GitLab CI, or other CI systems, you need separate integrations for each.

BuildButler gives you:

One configuration for all CI systems — the same JSON rules work across Jenkins, GitHub Actions, GitLab CI, TeamCity, and BuildKite
CI analytics alongside TCM — build trends, flaky test detection, test history, and Ask AI — not just result pushing
Pattern-based routing — glob patterns match jobs to Xray projects automatically, no per-job configuration
Additional integrations — sync results to TestRail, ALM, or Zephyr Scale from the same platform

If you only use Jenkins and only need Xray, the native plugin is fine. If you use multiple CI systems or want analytics on top, BuildButler is the better fit.

Configuration example

[
  {
    "jobPattern": "backend/*",
    "jiraProject": "BACK",
    "testPlan": "BACK-100",
    "testEnvironment": "staging",
    "searchMode": "name"
  },
  {
    "jobPattern": "frontend/*",
    "jiraProject": "FRONT",
    "testPlan": "FRONT-200",
    "testEnvironment": "production",
    "searchMode": "name"
  }
]

Configuration fields

Field	Type	Required	Description
`jobPattern`	string	Yes	Glob pattern to match CI job names
`jiraProject`	string	Yes	Jira project key (e.g. `BACK`, `FRONT`)
`testPlan`	string	No	Xray test plan issue key to associate executions with
`testExecution`	string	No	Existing test execution issue key. If omitted, a new one is created.
`testEnvironment`	string	No	Xray environment name (e.g. `staging`, `production`)
`searchMode`	string	No	Match existing test cases by `name` or `path`. Default: `name`
`revision`	string	No	Source code revision to record
`labels`	string[]	No	Jira labels to apply to created test issues

Supported CI systems

Xray integration works with all CI systems BuildButler supports:

Jenkins (Local plugin or Cloud API)
GitHub Actions
GitLab CI
TeamCity
BuildKite

Getting started

Sign up for BuildButler (free tier includes Xray integration)
Connect your CI system
Configure your Xray/Jira credentials in System Settings
Define your job mapping rules
Run a build — test results appear as Xray test executions in Jira

See the full Xray configuration reference for all available fields.