...
Event Id of the Jenkins custom event: Custom plugin needs a custom event to be raised whenever when ever we try to trigger the Jenkins job from Jira. This custom event can be created in the in the administration section of Jira. Jira administrator will have to create this custom event, associate it with any notification scheme and make a note of its id. User configuring the plugin can then put this id of the custom event in this configuration textbox
‘Test Execution' issue type Id: This configuration needs the issue type id of the ‘Test Execution’ issue type. We can get this detail from the 'issues’ menu in the administration section.
‘Test' issue type id: This configuration needs the issue type id of the 'Test’ issue type. We can get this detail from the 'issues’ menu in the administration section
Id of the custom field which lists the Jenkins Jobs on the issue details screen: Custom plugin also comes with a custom field which is called as ‘Jenkins Job Selector'. Plugin admin needs to add this custom fields to proper screen(Create, Edit and view) in Jira. This field is used to map an already configured Jenkins job to a Xray Test. We will see about how to configure Jenkins job in the custom plugin in the ‘Job Mappings’ screen. In the current configuration we have to give the custom field id of this 'Jenkins Job selector’ field. Please note that we have to append 'customfield_' in front of the actual custom field id while specifying its value in the textbox.
Users of these groups can modify the Jenkins plugin data: Here we can provide the name of the group or groups(comma separated values) members of which can edit the data in different screen of this custom plugin. If this field is left empty then only the Jira administrator can access the details of configuration of the custom plugin and can view its different screens.
Default Jira Integration account to be user for updates: This is a Jira account which is a service account which is required by the plugin to make updates to xray test statuses and to pull attachments to Jira from Jenkins.
Custom field Id of the field which stores link for Xray between Tests and Test Execution: This is a custom field used by Xray to identify Test associated with Test Executions. Please note that we have to append 'customfield_' in front of the actual custom field id while specifying its value in the textbox.
Audit log
This screen shows the logs of different events happening in the plugin at runtime. Please note that these are the events which occur on the Jira side of the plugin. This screen doesn’t capture the details of the events(logs) from Jenkins jobs. Those will be available to the users of the jenkins under the console logs under each run of the job
...
Attaching the Xray Test to Xray Test Execution:
To trigger the Jenkins jobs connected to each Test and to get the result status and the TestComplete custom report, we need to trigger the process using a Test Execution. Test Execution acts as a container for different Tests. It can hold both Manual Tests as well as Jenkins related Tests under it. The first step would be test add a Test under a Test Execution. That can be done by adding the existing Tests that we created as a part of previous steps to the Test Execution.
...
Please note that we can attach data sheets required by the Jenkins Job(or TestComplete script) to the current TestExecution as an attachment.
...
Once this is done then we can trigger the custom event using the menu item that appears under each Test Execution in the 'More' options dropdown on the issue details screen.
...
Clicking on this menu-item will trigger each job connected to each Test under the current Test Execution. As and when the Jenkins job complete their execution the test results will be posted back to Jira along with the custom reports(which will be attached(one attachment per Xray Test) to Test Execution as attachments).
...