The following plugin provides functionality available through
Pipeline-compatible steps. Read more about how to integrate steps into your
Pipeline in the
section of the
For a list of other such plugins, see the
Pipeline Steps Reference
aioImport: Publish results to AIO Tests - Jira
projectKey : String
Jira Project key (eg. SCRUM) to which the results need to be reported to
resultsFilePath : String
Path to results file which needs to be uploaded. Path needs to be relative to workspace eg. /target/surefire-reports/testng-results.xml
addCaseToCycle : boolean
If checked, cases not already in cycle are added, else the cases are reported as errors
createCase : boolean
If checked and no case exists with a matching case key or automation key, a new case is created
bddForceUpdateCase : boolean
If checked, cases will be updated with scenario steps if they mismatch. Select if feature files from automation code repo are source of truth.
createNewRun : boolean
If checked, a new run will be created for each execution of case. If unchecked, the existing latest run would be overwritten with execution data.
API Token from AIO Tests - to move to credentials or global config
frameworkType : String (optional)
Nested Choice of Objects
failBuildOnFailure : boolean (optional)
If checked, the build result will be updated to failed, in case publishing results fails
hideDetails : boolean (optional)
If checked, case details from the publish results response will be hidden in job console log. If unchecked, status would be shown against each case that was published.
jiraInstanceType : String (optional)
Jira Server Password
jiraServerUrl : String (optional)
Jira Server IP address or hostname eg. https://yourjiraserver.com
jiraUsername : String (optional)
Jira Server Username
Was this page helpful?
Please submit your feedback about this page through this
Alternatively, if you don't wish to complete the quick form, you can simply
indicate if you found this page helpful?
See existing feedback here.