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

Build and Publish Add-on Products on SAP Cloud Platform ABAP Environment: Move limitations to top (#2412)

Browse Source 
* Move limitations to top

* Remove blank line

* Update abapEnvironmentAddons.md
This commit is contained in:
Peter Persiel
2020-11-22 17:25:34 +01:00
committed by GitHub
parent 008055237c
commit 5e4e438d8e
1 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2,8 +2,9 @@
## Introduction
!!! caution "Not yet released"
This scenario is not yet available. It is still work in progress and will be released at a later time.
!!! caution "Initial Scope"
The initial scope supports an add-on product consisting of **one** software component. Furthermore, this software component can not be used in multiple add-on products.
You cannot build add-ons based on gCTS branching functionality.
This scenario describes how an add-on for the SAP Cloud Platform ABAP Environment is built. It is intended for SAP partners who want to provide a Software as a Service (SaaS) solution on the SAP Cloud Platform using the ABAP Environment. Therefore, a partner development contract (see [SAP PartnerEdge Test, Demo & Development Price List](https://partneredge.sap.com/en/library/assets/partnership/sales/order_license/pl_pl_part_price_list.html)) is required. This page aims to provide an overview of the build process of the add-on.
@ -15,10 +16,6 @@ Of course, this tackles only the upstream part of the SaaS solution lifecycle. O
The installation and maintenance of ABAP software is done / controlled via software product versions. A **software product version** is a „bundle" of software component versions made available at the same time for implementing a well-defined scope of functionality. It is the technical / delivery view on a software portfolio.
!!! caution "Initial Scope"
The initial scope supports an add-on product consisting of **one** software component. Furthermore, this software component can not be used in multiple add-on products.
All packages of a software component must have the same namespace as the software component itself. And initially only the master branch of software components shall be used.
### Software Product Version
A software product version is defined by a name and a version string. The name of a software product is a string with a maximum of 30 characters and consists of the [namespace](https://launchpad.support.sap.com/#/notes/84282) and a freely chooseble part - `/NAMESPC/PRODUCT1`. The version string consists of three numbers separated by a dot - `1.2.0`. The numbers in the version string have a hierarchic relationship: