GitLab Integration

Example GitLab integration

The below workflow diagram describes a potential GitLab Integration scenario as part of an overall ActiveControl workflow. A JIRA integration is also depicted in this example.

Figure: Potential Gitlab (and JIRA) integration reflected as part of an ActiveControl workflow

Key Points of a bi-directional GitLab integration

Outbound Integration

i) When transports land in a (configurable) Control Point location within the ActiveControl workflow, the outbound integration is triggered.

ii) A payload is sent by ActiveControl to GitLab, containing all relevant field information relating to the associated Business Tasks and Transport Forms. This would likely include Custom Field information, where the Transport Form owner (ie Developer or Functional) or other such SAP resource could record the relevant automated test scripts to be run.

iii) ActiveControl can also automatically lock the Import Queue at this point (since in most circumstances, a customer would not want further transports to be imported whilst an automated testing cycle is running).

iv) On receiving the payload, Gitlab would process and trigger the relevant automated testing within the Customers testing tool.

Inbound Integration

i) On completion of automated testing cycle, GitLab would receive pass/fail information back from the automated testing tool, and send this back to ActiveControl.

ii) ActiveControl would process this pass/fail information, and move the associated Business Tasks / Transport Forms forward to the next location in the workflow (in the event of successful automated testing).

iii) ActiveControl would automatically unlock the Import Queue, so that subsequent transports/changes can again be imported to the SAP system.