Background

ActiveControl includes an out-of-the-box Integration Framework which enables bi-directional integration capabilities with ITSM products such as JIRA, ServiceNow and HPSM and also more recently with DevOps lifecycle tools such as Gitlab.

During early 2020, this Integration capability has been extended to include an integration with Jenkins, another third-party DevOps product used increasingly within IT organisations to automate aspects of software development building, testing and deployment. Basis Technologies believes that this new Jenkins integration will enable SAP customers to further evolve their continuous integration and continuous delivery (CI/CD) capabilities in delivering SAP change as part of an ActiveControl workflow.

The initial use-case for which this Jenkins integration was built by Basis Technologies was to trigger automated testing scripts within tools such as Selenium or Tosca, as part of an ActiveControl workflow, however the reality is that this new integration could potentially be adapted to fulfil numerous other Jenkins-triggered scenarios in the future to help Basis Technologies’ customers become more automonous in their delivery of SAP change.

The rest of this Integration Guide aims to detail the functional and technical solution for the new ActiveControl / Jenkins integration to trigger automated testing.

! The Jenkins integration for automated testing is currently not an out-of-the-box ‘plug it and play’ Integration in the sense of many of the more established ActiveControl integrations such as JIRA and ServiceNow. Setting up this Jenkins Integration in a customer environment will require a combination of ActiveControl, Jenkins and the Automated Testing tool Administrator resources to be involved from the Customer side, in addition to the Basis Technologies team. Some coding will also be required on the customer side, to trigger the automated testing from Jenkins, and then pass back the information to ActiveControl.