Jenkins Integration

Basis Technologies have developed an ActiveControl integration with Jenkins as part of a Customer Pilot. The purpose of this integrations is to achieve an automated CI//CD workflow by the triggering of automated tests.

• For the Outbound integration, When transports arrive in a QA Test Queue ActiveControl will send a (configurable) URL request to Jenkins containing the Business Task details, to trigger some automated testing.
  As part of this Outbound integration, the Integration will automatically lock the ActiveControl Import Queue (to prevent further transports being imported for the duration of the automated tests).

• For the Inbound integration, ActiveControl will receive back a Pass/Fail from Jenkins, and assuming a Pass, automatically add a Test Sign-off result into the associated Business Task(s) and then move them forward in the workflow to the subsequent Control Point. (E.g. for UAT to then be performed)

Configuration Steps

The Jenkins Integration is detailed in a separate Integration Administration Guide, which is available here.