A project administrator configures the connection and selects which project, cycle, environment and build values Nexus sends.
Nexus capability guide
Connect automation to release evidence
Run in CI starts a configured GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines job. The pipeline executes the tests and returns results to the same cycle.
Jira issue recordsHuman-reviewed AI draftsConnected execution evidence
How it works
Start a pipeline from the cycle
Run in CI starts a configured GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines job. The pipeline executes the tests and returns results to the same cycle.
Match test results by Automation Key or issue key.
Record pass/fail per run and raise linked Jira Bugs for failed runs.
Use the customer-hosted Nexus runner for self-hosted Jenkins or GitLab.
Questions buyers ask
Frequently asked questions
Where does automation run?
Your CI service or customer-hosted runner executes the tests. Nexus records the results in Jira.
Does AI create accepted tests automatically?
No. A person reviews and accepts every draft. Your organisation connects its own supported AI account.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.