1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-12 10:55:20 +02:00

Long commit in piper documentation (#2728)

* Warning for long commit ID

* Update abapEnvironmentAddons.md

* How to find long commit
This commit is contained in:
Christian Luttenberger 2021-03-28 10:44:14 +02:00 committed by GitHub
parent 03f46ef90c
commit d15b67f882
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 0 deletions

View File

@ -45,6 +45,10 @@ stages:
### addon.yml
!!! caution "Use Long Commit ID for the commitID fields"
Please use the long commit ID in the commit ID field currently if you are using the short commit ID the build process will fail.
Go into the Manage Software Components app, navigate to the branch, select the commit in the list of commits, field "Long Commit ID" becomes available.
```YAML
---
addonProduct: /NAMESPC/PRODUCTX

View File

@ -140,6 +140,10 @@ A configuration file `.pipeline/config.yml` is used to provide all required valu
The build process is controlled by an add-on descriptor file called `addon.yml`. This file must be created manually and must be stored in the GIT repository of the pipeline. It must contain information about the to-be-delivered [add-on product version](#add-on-product-version) and the contained [software component versions](#software-component-version). Below, you see an example:
!!! caution "Use Long Commit ID for the commitID fields"
Please use the long commit ID in the commit ID field currently if you are using the short commit ID the build process will fail.
Go into the Manage Software Components app, navigate to the branch, select the commit in the list of commits, field "Long Commit ID" becomes available.
```YAML
---
addonProduct: /NAMESPC/PRODUCTX