The ActiveControl / GitLab integration outbound integration works by ActiveControl calling GitLab
Customer GitLab Administrators would need to setup GitLab for the purpose of the Integration with ActiveControl. This would be used to as part of the ActiveControl outbound integration, to perform the relevant GitLab-side action ie triggering automated testing scripts within tools such as Selenium or Tosca. They would also be used to trigger events as part of Inbound Integration back to ActiveControl
The likely events as part of outbound and inbound integration are as follows:
| Number | Event |
|---|---|
| 1 | ActiveControl 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 from ActiveControl to GitLab |
| 3 | GitLab initiating the required Tests within the automated testing tool. |
| 4 | GitLab receiving PASS or FAIL test result information from the automated testing tool, and sending this back to ActiveControl. |
| 5 | ActiveControl 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. |
Post your comment on this topic.