jenkins-library (Project Piper) is an Apache-2.0 Jenkins shared library from SAP that supplies default continuous delivery pipelines and a set of reusable pipeline "steps" for teams building CI/CD around SAP systems.

What it is

jenkins-library is the shared library component of Project "Piper". It lives in the Jenkins ecosystem and is written in Go, with the repository topics describing it as ci-cd, cli, golang, jenkins, and open-source. The project offers default pipelines that implement CI/CD processes integrating SAP systems, and the shared library adds a set of steps for building scenarios that go beyond those defaults. Documentation is published at https://sap.github.io/jenkins-library/, with the project homepage at https://www.project-piper.io.

The concrete problem it solves is pipeline scripting from scratch. Instead of every team hand-writing Jenkinsfiles and re-implementing the same build, test and deployment logic, teams adopt the default pipelines and then extend them with shared steps. The specific thing it replaces is bespoke, per-repository Jenkins pipeline code, which is why the library is consumed as a Jenkins shared library rather than copied between jobs.

Key capabilities

• Provides default CI/CD pipelines for integrating SAP systems, intended to be used directly as a starting point.
• Exposes a shared library of "steps" so teams can compose custom scenarios beyond the default pipelines.
• Implemented in Go, with the repository topics listing golang and cli alongside ci-cd and jenkins.
• Licensed under Apache-2.0 and carries a REUSE status badge for licensing compliance.
• Quality signals published through CodeClimate maintainability and test coverage badges plus a Go Report Card badge.
• User documentation hosted at https://sap.github.io/jenkins-library/.
• Bugs, feature requests and general feedback handled through the GitHub issues page, with updates and questions through the Project Piper google group.

Who uses it and how

• SAP internal development teams consuming Piper through internal platforms, whose access and support continue uninterrupted by the archive plan.
• External teams running Jenkins pipelines against SAP systems, starting from the default pipelines and extending them with shared steps.
• Teams with non-standard delivery flows that use the step library to build their own scenarios rather than editing the defaults.
• Contributors following CONTRIBUTING.md before opening pull requests, and users filing issues or asking questions on the google group.
• External users planning migration, who are directed to contact their SAP representative for alternatives and migration paths.

Getting started

The README does not give a package name, Docker image or install command; it points to the User Documentation for Project Piper at https://sap.github.io/jenkins-library/ as the entry point. Start there, and treat a working Jenkins installation as the prerequisite since this is a Jenkins shared library.

How it compares

No paid products or comparable tools are named in the facts, so this project stands alone in this registry rather than being contrasted against alternatives. It is SAP-specific in purpose, which means its closest substitute is a team's own Jenkins pipeline code, not another catalogued project.

When to use it — and when not to

The repository will be archived on December 31, 2026, and from January 1, 2027 it becomes read-only; between now and then only critical issues receive maintenance, so anyone outside SAP should plan a migration rather than adopt it for new long-lived work. A self-hoster must run and maintain their own Jenkins controller and agents, and the README excerpt is sparse on setup detail, offering documentation links rather than installation instructions. SAP internal teams on internal platforms are the clear exception, since their access and support continue without interruption.