jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2025-11-06 09:09:19 +02:00
Code Issues Releases Activity

Add transport request to GPP (#3862)

Browse Source 
* Add TransportRequestUploadCTS step to Release

* typo comma

* test transportRequest git ID

* Update piperPipelineStageInit.groovy

* add echo

* aggressive echo

* Update piperPipelineStageInit.groovy

* remove echo + add unitTests

* fix typos and documentation syntax

* test documentation syntax

* test documentation syntax

* Switch to shell

* Documentation changes

* Add review changes

* Remove echo

* Refactor test cases

Co-authored-by: Kondreddy <srinikitha.kondreddy@sap.com>
Co-authored-by: Oliver Feldmann <oliver.feldmann@sap.com>
Co-authored-by: Roland Stengel <r.stengel@sap.com>
This commit is contained in:
Jesse Awan
2022-07-22 15:15:53 +02:00
committed by GitHub
parent 5fb43a9ead
commit 274c11d28f
7 changed files with 106 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/docs/steps/transportRequestReqIDFromGit.md
View File

@@ -14,6 +14,18 @@ See [transportRequestUploadSOLMAN](transportRequestUploadSOLMAN.md).
With `transportRequestReqIDFromGit` you can retrieve the transport request ID from the commit message of the Git repository of your project. This way, you can address the transport request without having to change the setup of your pipeline.
Please make sure that the ID is unique in the defined search range.
## General Purpose Pipeline Init Stage
The step can also be configured via General Purpose Pipeline in Init stage using the config.yml as follows:
```yaml
stages:
Init:
transportRequestReqIDFromGit: true
```
This will initialize the step within the Init stage of the pipeline and retrieve the `transportRequestId` from the git commit history.
### Specifying the Git Commit Message
`transportRequestReqIDFromGit` searches for lines that follow a defined pattern in the Git commit messages (`git log`) of your project.

14
documentation/docs/steps/transportRequestUploadCTS.md
View File

@@ -36,7 +36,7 @@ To create an own Docker image with the [SAP Fiori tools](https://help.sap.com/vi
1. Push your image to your private [Docker Hub registry](https://hub.docker.com/):
```/bin/bash
docker push my/fiori-node
docker push my/fiori-node
```
1. Add the following content to your `config.yml` file:
@@ -138,6 +138,18 @@ transportRequestReqIDFromGit( script: this )
transportRequestUploadCTS( script: this, ... )
```
## General Purpose Pipeline Release Stage
The step can also be configured via General Purpose Pipeline in Release stage using the config.yml as follows:
```groovy
stages:
Release:
transportRequestUploadCTS: true
```
This will initialize the step within the Release stage of the pipeline and will upload the desired application (SAPUI5/OPENUI5) to the SAPUI5 ABAP repository.
## ${docGenParameters}
## ${docGenConfiguration}