jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-12 10:55:20 +02:00
Code Issues Releases Activity
77e9b04e69
sap-jenkins-library/documentation/docs/index.md

4.6 KiB
Raw Blame History

Project "Piper" User Documentation

Continuous delivery is a method to develop software with short feedback cycles. It is applicable to projects both for SAP Cloud Platform and SAP on-premise platforms. SAP implements tooling for continuous delivery in project "Piper". The goal of project "Piper" is to substantially ease setting up continuous delivery in your project using SAP technologies.

What you get

To get you started quickly, project "Piper" offers you the following artifacts:

  • A set of ready-made Continuous Delivery pipelines for direct use in your project
  • A shared library that contains reusable step implementations, which enable you to customize our preconfigured pipelines, or to even build your own customized ones
  • A set of Docker images to setup a CI/CD environment in minutes using sophisticated life-cycle management

To find out which offering is right for you, we recommend to look at the ready-made pipelines first. In many cases, they should satisfy your requirements, and if this is the case, you don't need to build your own pipeline.

The best-practice way: Ready-made pipelines

Are you building a standalone SAP Cloud Platform application?
 Then continue reading about our general purpose pipeline, which supports various technologies and programming languages.

Are you building an application with the SAP Cloud SDK and/or SAP Cloud Application Programming Model?
 Then we can offer you a pipeline specifically tailored to SAP Cloud SDK and SAP Cloud Application Programming Model applications

The do-it-yourself way: Build with Library

The shared library contains building blocks for your own pipeline, following our best practice Jenkins pipelines described in the Scenarios section.

The best practice pipelines are based on the general concepts of Pipelines as Code, as introduced in Jenkins 2. 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.

For an example, you might want to check out our "Build and Deploy SAPUI5 or SAP Fiori Applications on SAP Cloud Platform with Jenkins" scenario.

Extensibility

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.

API

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.