The ABAP Environment pipeline makes use of APIs of the SAP BTP (esp. cf cli) and SAP BTP, ABAP environment (project name "Steampunk"). While the pipeline contains a fixed set of steps and stages, it is possible to adapt it using different configurations. This repository shows and explains different examples of these configurations.
To create the examples shown in this repository yourself, a Jenkins server and the entitlements for SAP BTP, ABAP environment are required.
Please have a look at the documentation of the piper project to learn more about the configurations necessary to run the examples in this repository.
A Jenkins pipeline is defined by a "Jenkinsfile" and other pipeline specific configuration files. The examples in this repository consist of all required files for a specific use case. The folders ".reuse" and "LICENSES" are required for this Open Source project and do not belong to the pipeline configuration.
If you want to recreate a specifc use case, you can copy the associated files and replace the context specifc values (API Endpoints, Jenkins Credential IDs etc.)
- Running ATC checks & AUnit tests on a transient ABAP Environment system
- Running ATC checks & AUnit tests on a static ABAP Environment system
- Build add-ons on a transient ABAP Environment system (SAP Partner use case)
- Build add-ons on a static ABAP Environment system (SAP Partner use case)
This project is only updated by SAP employees.
A list of known issues is available on the GitHub issues page of this repository.
Copyright (c) 2020 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.