jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2025-03-03 15:02:35 +02:00
Code Issues Releases Activity

Merge branch 'PR1041' of github.com:rodibrin/jenkins-library into PR1041

Browse Source
This commit is contained in:
Stengel 2019-12-10 11:33:51 +01:00
commit ed581fab96
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
documentation/docs/guidedtour.md
View File

@ -85,29 +85,29 @@ Copy the sources of the application into your own Git repository. While we will
<p align="center">
![Create Pipeline Job](images/JenkinsNewItemPipeline.png "Jenkins New Item")
</p>
**Note:** The ready-made Continuous Delivery pipelines of project "Piper" require to run as **Multibranch Pipeline**.
**Note:** The ready-made continuous delivery pipelines of project "Piper" must run as **Multibranch Pipeline**.
1. For **Branch Sources**, choose **Add source**, and select the **Git** as source repository.
1. For **Branch Sources**, choose **Add source**, select **Git** as source repository.
<p align="center">
![Create Pipeline Job](images/JenkinsNewItemPipeline-AddSource.png "Branch Sources - Add source")
</p>
1. For **Project Repository** in the **Git** section, enter the URL of your Git repository, for example `https://github.com/<your-org>/cloud-cf-helloworld-nodejs`. **Note:** If your repository is protected, you must provide your credentials in **Credentials**.
1. For **Discover branches**, choose **Add** and select **Filter by name (with wildcards)**.
1. For **Discover branches**, choose **Add** and **Filter by name (with wildcards)**.
<p align="center">
![Create Pipeline Job](images/JenkinsNewItemPipeline-DiscoverBranch.png "Discover branches - Add")
</p>
While a multibranch pipeline can execute different Jenkinsfiles for different branches, here, we will configure the pipeline of a single branch only.
A multibranch pipeline can execute different Jenkinsfiles for different branches. In this case, however, configure the pipeline of a single branch only.
1. For **Include** in the **Filter by name** section, enter the branch name `1_REST_persist_in_Memory`.
<p align="center">
![Create Pipeline Job](images/JenkinsNewItemPipeline-FilterByName.png "Discover Branches - Filter By Name")
</p>
1. Choose **Save**. **Result:** Jenkins scans the repository for branches and filters them according the specified **Includes**. If the branch is detected, it will be build afterwards.
1. Choose **Save**. **Result:** Jenkins scans the repository for branches and filters them according to the specified **Includes**. If the branch is detected, it is built.
For additional information about multibranch pipelines please refer to the [Jenkins documentation][jenkins-io-multibranch].
For additional information about multibranch pipelines, please refer to the [Jenkins documentation][jenkins-io-multibranch].
## Add a Build Step
@ -194,8 +194,8 @@ Open the application name to get into the `Application Overview`. Open the **App
## What's Next
You are now familiar with the basics of using project "Piper". Through the concept of pipeline as code, project "Piper" and Jenkins pipelines are extremely powerful. While Jenkins pipelines offer a full set of common programming features, project "Piper" adds SAP-specific flavors. Have a look at the different **Scenarios** to understand how to easily integrate SAP systems with defaults.
Dive into the ready-made Continuous Delivery pipelines: the **General Purpose Pipeline**
and **SAP Cloud SDK Pipeline** help you to quickly build and deliver your apps.
Dive into the ready-made continuous delivery pipelines: the **General Purpose Pipeline**
and **SAP Cloud SDK Pipeline** help you quickly build and deliver your apps.
Browse the steadily increasing list of features you can implement through the project "Piper" **Steps**.
The **Configuration** pattern supports simple pipelines that can be reused by multiple applications. To understand the principles of inheritance and customization, have a look at the the [configuration][resources-configuration] documentation.