The ActiveControl / Jenkins integration outbound integration works by ActiveControl calling Jenkins pipeline build.
Customer Jenkins Administrators would need to setup this Jenkins pipeline for the purpose of the Integration with ActiveControl. This would be used to as part of the ActiveControl outbound integration, to perform the relevant Jenkins-side action ie triggering automated testing scripts within tools such as Selenium or Tosca. They would also be used to trigger events in ActiveControl as part of Inbound Integration.
The likely events as part of outbound and inbound integration are as follows:
| Number | Event |
|---|---|
| 1 | Locking the Import Queue (to prevent the import of subsequent transports whilst the Integration is in progress. |
| 2 | Passing contents of the Test Queue / Required Tests |
| 3 | Initiate the required Tests |
| 4 | Sending PASS or FAIL test result information back to ActiveControl. |
| 5 | Unlocking the Import Queue at the end of Inbound integration. |
| 6 | Uploading Test results to the Business Task, and moving the associated Transport Forms forward to the next location in the workflow. |
Figure: Example of Jenkins Pipeline to support automate testing.
Post your comment on this topic.