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

Update abapEnvironmentAddons.md: Further version limitations (#3263)

Browse Source 
* Update abapEnvironmentAddons.md
This commit is contained in:
Peter Persiel 2021-11-11 13:56:05 +01:00 committed by GitHub
parent b42534e619
commit df441683f7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
documentation/docs/scenarios/abapEnvironmentAddons.md
View File

@ -3,7 +3,7 @@
!!! caution "Current limitations"
gCTS-related restrictions apply, please refer to [gCTS: restrictions in supported object types](https://launchpad.support.sap.com/#/notes/2888887)
!!! caution Required project "Piper" library version
!!! caution "Required project "Piper" library version"
SAP BTP ABAP environment releases might require certain versions of the project "Piper" Library. More Information can be found in [SAP Note 3032800](https://launchpad.support.sap.com/#/notes/3032800).
## Introduction
@ -204,6 +204,11 @@ Invalid increase:
- 2.1.0 to 2.3.0 (version 2.2.0 is missing; therefore, a support package level is missing)
- 2.1.1 to 2.1.3 (version 2.1.2 is missing; therefore, a patch level is missing)
Technically, the allowed number range for add-on product version and software component version is 1.0.0 to 9999.9999.9999.
The support package level of software component version can only go up until 369 because of technical limitations.
For the patch level, there is a technical limit of 36³, limited to 9999.
### Example
Please have a look at the configuration example to [build and publish add-on products using a transient assembly system](https://github.com/SAP-samples/abap-platform-ci-cd-samples/tree/addon-build).