An efficient software development process is vital for success in building business applications on SAP Cloud Platform or SAP on-premise platforms. SAP addresses this need for efficiency with project "Piper". The goal of project "Piper" is to substantially ease setting up continuous delivery processes for the most important SAP technologies by means of Jenkins pipelines.
Project "Piper" consists of two parts:
- A shared library containing steps and utilities that are required by Jenkins pipelines.
- A set of Jenkins pipelines using the piper library to implement best practice processes.
Please follow this link to our extended library documentation.
The shared library contains all the necessary steps to run our best practice Jenkins pipelines.
The best practice pipelines are based on the general concepts of Jenkins 2.0 Pipelines as Code. With that you have the power of the Jenkins community at hand to optimize your pipelines.
You can run the best practice Jenkins pipelines out of the box, take them as a starting point for project-specific adaptations or implement your own pipelines from scratch using the shared library.
If you consider adding additional capabilities to your Jenkinsfile, consult
the Jenkins Pipeline Steps Reference. There, you get an
overview about steps that are natively supported by Jenkins.
The Jenkins shared libraries concept helps you to extract reusable parts from your pipeline and to keep your pipeline code small and easy to maintain.
Custom library steps can be added using a custom library according to the
Jenkins shared libraries concept instead of adding
groovy coding to the Jenkinsfile. Your custom library can coexist next to the
provided pipeline library.
All steps (vars and resources directory) are intended to be used by Pipelines and are considered API.
All the classes / groovy-scripts contained in the src folder are by default not part of
the API and are subjected to change without prior notice. Types and methods annotated with
@API are considered to be API, used e.g. from other shared libraries. Changes to those
methods/types needs to be announced, discussed and agreed.
- Java Runtime Environment 8
- Installation of Jenkins v 2.60.3 or higher running on Linux. We tested with debian-stretch.
- Jenkins Plugins installed as described in the Required Plugin section.
- A Jenkins user with administration privileges.
- The Jenkins instance has access to github.com.
To setup the shared library, you need to perform the following steps:
- Login to your Jenkins instance with administration privileges.
- Open the system configuration page (Manage Jenkins > Configure System).
- Scroll down to section Global Pipeline Libraries and add a new Library by
clicking the Add button.
- set Library Name to
piper-lib-os - set Default Version to the branch or tag you want to consume (e.g.
masterorv0.1) - set Retrieval Method to
Modern SCM - set Source Code Management to
Git - set Project Repository to
https://github.com/SAP/jenkins-library
- set Library Name to
- Save changes
Now the library is available as piper-lib-os and can be used in any
Jenkinsfile by adding this line:
@Library('piper-lib-os') _Jenkins will download the library during execution of the Jenkinsfile.
A list of known issues is available on the GitHub issues page of this project.
Feel free to open new issues for feature requests, bugs or general feedback on the GitHub issues page of this project.
Register to our google group in order to get updates or for asking questions.
Read and understand our contribution guidelines before opening a pull request.
Copyright (c) 2017 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, v. 2 except as noted otherwise in the LICENSE file