- Install the plugin using the
Jenkins Plugin Managerand restart Jenkins.
- Go to the global configuration page (
Manage Jenkins > Configure System).
- Find the AbapCi Plugin Section and specify and the
connection infofor your ABAP development system.
- Create a new
Jenkins jobfor an ABAP Package of your ABAP Dev System (freestyle project or pipeline project)
This plugin provides the foundation to integrate an ABAP on premise system into Jenkins.
Currently there are two Continuous Integration features supported (run on an ABAP package):
- running ATC checks
- running Unit tests + coverage
The plugin can be used as a build step in a free-style project or also within a pipeline project.
In the Jenkins global configurations multiple systems can be set with connection info and a label, which is then later used for referencing this system in freestyle projects or pipelines. The following parameters have to be specified:
- Port - in the most cases this should be the standard port 8000 for HTTP
- Protocol: http or https
Sample configuration to an ABAP development system instance - Jenkins and ABAP system running in the AWS cloud
If you choose to integrate the plugin into a freestyle-project you can do this by using the plugin within a build step. Simply add the AbapCi Plugin as build step and specify the ABAP package and the features you want to perform on the configured package.
The AbapCi Plugin is pipline compatible. The script to integrate an ABAP system into a pipeline is shown below. In this sample two stages will be performed, first for the package in QA_1 system, second in QA_2 system. QA_1 and QA_2 are the labels set in the configuration. The notation to call the plugin is:
abapCi sapPackagename: 'ABAP_PACKAGENAME' [, runUnitTests: (true|false)] [, runAtcChecks: (true|false)], withCoverage: (true/false), sapSystemLabel: "ID"
A great help to get the right notation is to use the
Pipeline Syntax button which is located directly below the pipeline script box.