abapAddonAssemblyKitRegisterPackages¶
This step uploads the SAR archives and creates physical Delivery Packages in in the File Content Management System of SAP.
Description¶
This step takes the list of Software Component Versions from the addonDescriptor in the commonPipelineEnvironment. For Packages in status "P"lanned it uploads the SAR archive with the data file and metadata XML of the Delivery Packages composed and exported in the Final Assembly system. and creates physical Delivery Packages. The Packages ares saved in the File Content Management System of SAP. The new status "L"ocked is written back to the addonDescriptor in the commonPipelineEnvironment.
Usage¶
We recommend to define values of step parameters via config.yml file. In this case, calling the step is reduced to one simple line.
Calling the step can be done either via the Jenkins library step or on the command line.
Jenkins Pipeline¶
library('piper-lib-os') abapAddonAssemblyKitRegisterPackages script: this
Command Line¶
piper abapAddonAssemblyKitRegisterPackages
Outputs¶
Output type | Details |
---|---|
commonPipelineEnvironment |
|
Prerequisites¶
- The credentials to access the AAKaaS (e.g. S-User) must be stored in the Jenkins Credential Store
- This step needs the names of the packages which should be registered. For each package a SAR archive with the data file and metadata XML must be provided.
- The package names and their status are taken from the addonDescriptor in the commonPipelineEnvironment, as well as the SarXMLFilePath with the path to the SAR file.
- The information will be written to the commonPipelineEnvironment if you run prior to this step the step abapAddonAssemblyKitReserveNextPackages
- The SAR archive is produced if you run the step abapEnvironmentAssemblePackages
Parameters¶
Overview¶
Name | Mandatory | Additional information |
---|---|---|
addonDescriptor | yes | |
password | yes | |
script | yes | |
username | yes | |
abapAddonAssemblyKitEndpoint | no | |
verbose | no | activates debug output |
Details¶
abapAddonAssemblyKitEndpoint¶
Base URL to the Addon Assembly Kit as a Service (AAKaaS) system
Scope | Details |
---|---|
Aliases | - |
Type | string |
Mandatory | no |
Default | https://apps.support.sap.com |
Secret | no |
Configuration scope |
|
Resource references | none |
addonDescriptor¶
Structure in the commonPipelineEnvironment containing information about the Product Version and corresponding Software Component Versions
Scope | Details |
---|---|
Aliases | - |
Type | string |
Mandatory | yes |
Default | $PIPER_addonDescriptor (if set) |
Secret | no |
Configuration scope |
|
Resource references | commonPipelineEnvironment: reference to: abap/addonDescriptor |
password¶
Password for the Addon Assembly Kit as a Service (AAKaaS) system
Scope | Details |
---|---|
Aliases | - |
Type | string |
Mandatory | yes |
Default | $PIPER_password (if set) |
Secret | yes |
Configuration scope |
|
Resource references | none |
script¶
Jenkins-specific: Used for proper environment setup.
The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with the this
parameter, as in script: this
. This allows the function to access the commonPipelineEnvironment
for retrieving, e.g. configuration parameters.
Scope | Details |
---|---|
Aliases | - |
Type | Jenkins Script |
Mandatory | yes |
Default | |
Secret | no |
Configuration scope |
|
Resource references | none |
username¶
User for the Addon Assembly Kit as a Service (AAKaaS) system
Scope | Details |
---|---|
Aliases | - |
Type | string |
Mandatory | yes |
Default | $PIPER_username (if set) |
Secret | yes |
Configuration scope |
|
Resource references | none |
verbose¶
verbose output
Scope | Details |
---|---|
Aliases | - |
Type | bool |
Mandatory | no |
Default | false |
Possible values | - true - false |
Secret | no |
Configuration scope |
|
Resource references | none |
abapAddonAssemblyKitCredentialsId¶
Jenkins-specific: Used for proper environment setup. See using credentials for details.
Credential stored in Jenkins for the Addon Assembly Kit as a Service (AAKaaS) system
Scope | Details |
---|---|
Aliases | - |
Type | string |
Configuration scope |
|
Examples¶
Configuration in the config.yml¶
The recommended way to configure your pipeline is via the config.yml file. In this case, calling the step in the Jenkinsfile is reduced to one line:
abapAddonAssemblyKitRegisterPackages script: this
The config.yml should look like this:
steps: abapAddonAssemblyKitRegisterPackages: abapAddonAssemblyKitCredentialsId: 'abapAddonAssemblyKitCredentialsId', abapAddonAssemblyKitEndpoint: 'https://myabapAddonAssemblyKitEndpoint.com',
Input via the CommonPipelineEnvironment¶
Mandatory fields:
{"addonProduct":"", "addonVersion":"", "addonVersionAAK":"", "addonUniqueID":"", "customerID":"", "AddonSpsLevel":"", "AddonPatchLevel":"", "TargetVectorID":"", "repositories":[ { "name":, "tag":"", "branch":"", "version":"", "versionAAK":"", "PackageName":"SAPK001001REPOA", "PackageType":"", "SpLevel":"", "PatchLevel":"", "PredecessorCommitID":"", "Status":"P", "Namespace":"", "SarXMLFilePath":".pipeline/commonPipelineEnvironment/SAPK001001REPOA.SAR" }, { "name":"", "tag":"", "branch":"", "version":"", "versionAAK":"", "PackageName":"SAPK002001REPOB", "PackageType":"", "SpLevel":"", "PatchLevel":"", "PredecessorCommitID":"", "Status":"R", "Namespace":"", "SarXMLFilePath":".pipeline/commonPipelineEnvironment/SAPK002001REPOB.SAR" } ]}