You've already forked sap-jenkins-library
							
							
				mirror of
				https://github.com/SAP/jenkins-library.git
				synced 2025-10-30 23:57:50 +02:00 
			
		
		
		
	documentation - md image ref - html paragraph to center unsupported (#3217)
* remove html center for images
This commit is contained in:
		| @@ -73,33 +73,29 @@ Copy the sources of the application into your own Git repository. While we will | ||||
| 1. Save your changes to your remote repository. | ||||
|  | ||||
| 1. To set up a Jenkins job for your repository, open the Jenkins UI under `http://<jenkins-server-address>:<http-port>` and choose **New Item**. Per default, the `cx-server` starts Jenkins on HTTP port `80`. For more information, see the [Jenkins User Documentation][jenkins-io-documentation]. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 1. Provide a name for your new item (for example, *My First Pipeline*) and select **Multibranch Pipeline**. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|    **Note:** The ready-made continuous delivery pipelines of project "Piper" must 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**, select **Git** as source repository. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </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 **Filter by name (with wildcards)**. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|    A multibranch pipeline can execute different Jenkinsfiles for different branches. In this case, however, 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"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 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. | ||||
|  | ||||
| @@ -172,27 +168,24 @@ The `cloudFoundryDeploy`  step calls the Cloud Foundry command line client to de | ||||
|  | ||||
|    **Note:** look after the indentation of the step within the YAML. Specify the `organisation` and `space` properties. For more information about the configuration, see the [Common Configuration Guide][resources-configuration] and [cloudFoundryDeploy][resources-step-cloudFoundryDeploy]. | ||||
| 1. The key `CF_CREDENTIALSID` refers to a user-password credential you must create in Jenkins: In Jenkins, choose **Credentials** from the main menu and add a **Username with Password** entry. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 1. Save the Credential | ||||
|  | ||||
| 1. Save your changes to your remote repository. | ||||
|  | ||||
| 1. To run your pipeline, choose **Build Now** in the job UI. **Result:** The pipeline processed the three stages "prepare", "build" and "deploy". | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| If your pipeline fails, compare its files to the final [Jenkinsfile][guidedtour-sample.jenkins], the [config.yml][guidedtour-sample.config], and the [mta.yaml][guidedtour-sample.mta]. **Note**: YAML files are surprisingly sensitive regarding indentation. | ||||
|  | ||||
| ## Open Application | ||||
|  | ||||
| Your application has been deployed into your space in the Cloud Foundry space on SAP BTP. Login to SAP BTP and navigate into you space.   **Result:** Your space contains the application `piper.node.hello.world`, the state of the application is `Started`. | ||||
|    <p align="center"> | ||||
|  | ||||
|    | ||||
|    </p> | ||||
|  | ||||
| Open the application name to get into the `Application Overview`. Open the **Application Route** and add `/users` to the URL. **Result:** The application returns a list of user data. | ||||
|  | ||||
|   | ||||
| @@ -45,14 +45,12 @@ cat plugins.txt | awk '{system("java " "-jar jenkins-cli.jar -s http://localhost | ||||
| Shared libraries extending the Jenkins pipeline are defined within the Jenkins system configuration. A library is defined by a link to its source repository and an appropriate version identifier. To add the project "Piper"s library, execute the following steps: | ||||
|  | ||||
| 1. Open the Jenkins UI under `http://<jenkins-server-address>:<http-port>`, login with administration privileges, and choose **Manage Jenkins > Configure System**. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 1. Scroll down to section **Global Pipeline Libraries** and choose the **Add** button. A new library is created. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 1. For **Library Name**, enter `piper-lib-os`. | ||||
|  | ||||
| @@ -63,9 +61,8 @@ Shared libraries extending the Jenkins pipeline are defined within the Jenkins s | ||||
| 1. For **Source Code Management**, choose **Git**. | ||||
|  | ||||
| 1. For **Project Repository**, enter the GitHub URL of the project Piper shared library `https://github.com/SAP/jenkins-library`. | ||||
|    <p align="center"> | ||||
|     | ||||
|    </p> | ||||
|  | ||||
|      | ||||
|  | ||||
| 1. Save your changes. | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user