...

Currently (as of v3.6), this is not possible out-of-the-box yet. However, with some minor customization, this can be already be achieved as depicted in these ScriptRunner-related instructions.

Depending on the use case, this may be quite simple or a little more complex to implement.

...

• you just want to trigger a CI job, period; this job may be totally unrelated to the issue from where you triggered it
• what the CI job will do, including if it will report the results back to Xray or not, is not relevant

Image Removed

For most CI tools, this only requires that you perform some HTTP request passing the CI job as an argument, somehow.

...

Examples

• Automation for Jira
  • Trigger a Jenkins project build from an issue
• Jenkins Integration for Jira
  1. configure your Jenkins "site" (server) in the app settingImage Removed
  2. trigger the Jenkins "build" 
  3. Image RemovedImage Added
  4. Image RemovedImage Added
• ScriptRunner (these examples also report the results back to the current issue)
  • Trigger a Jenkins project build from a Test Plan
  • Trigger a Bamboo plan build from a Test Plan

Trigger a CI job and report back to the current issue

...

• you want to trigger a CI job and report back the results to the current issue (e.g. Test Plan)
• the tests that will run are unrelated with the caller issue; it's up to the logic built into the CI job to decide which tests to run

Image RemovedImage Added

"Jenkins Integration for Jira", "Automation for Jira", "ScriptRunner" apps can be used to implement this scenario.

...

• Jenkins Integration for Jira
  • in this case, you would need to use pipeline-based Jenkins projects where you would use a snippet of code to obtain the calling Jira issue which could be used later on in the step for uploading the results to Xray; you may need to enable the usage of these classes in Jenkins settings
    • def sourceIssueKey = currentBuild.getRawBuild().getCause(org.marvelution.jji.trigger.JiraCause).getIssueKey()
      
      1. configure your Jenkins "site" (server) in the app setting
         1. Image RemovedImage Added
      2. trigger the Jenkins "build" 
      3. Image RemovedImage Added
      4. Image RemovedImage Added
• Automation for Jira
  • Trigger a Jenkins project build from a Test Plan and report the results back to it
• ScriptRunner
  • Trigger a Jenkins project build from a Test Plan
  • Trigger a Bamboo plan build from a Test Plan

Trigger a CI job for the selected tests and report back to the current issue

...

• you want to trigger a CI job and report back the results to the current, caller issue (e.g. Test Plan, Test Execution)
• the tests that you want to run are the automated ones present in the caller issue (e.g. Test Plan, Test Execution)

Image RemovedImage Added

This scenario, though feasible, is a bit more complex for two reasons:

...

"ScriptRunner" app can be used to implement this scenario.

Examples

• ScriptRunner

  • Trigger a Jenkins project build from a Test Plan, for the Tests contained in the Test Plan

  • Trigger a Bamboo plan/stage build from a Test Plan, for the Tests contained in the Test Plan

References

• https://docs.automationforjira.com/
• https://docs.automationforjira.com/reference/smart-values.html