mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-01-16 05:16:08 +02:00
Update abapAddonAssemblyKitCheck.yaml (#4992)
* Update abapAddonAssemblyKitCheck.yaml remove bullet points as they are not rendered together with markdown * Update abapAddonAssemblyKitCheck.yaml * delete trailing space * go generate
This commit is contained in:
parent
82f6d58735
commit
d2285f8929
@ -70,11 +70,9 @@ func AbapAddonAssemblyKitCheckCommand() *cobra.Command {
|
||||
var createAbapAddonAssemblyKitCheckCmd = &cobra.Command{
|
||||
Use: STEP_NAME,
|
||||
Short: "This step calls AAKaaS to check the validity of the Addon Product Modelling.",
|
||||
Long: `This step does the following:<ul>
|
||||
[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)
|
||||
A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)
|
||||
The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
|
||||
</ul>
|
||||
Long: `[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml).
|
||||
A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules).
|
||||
The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage in subsequent pipeline steps.
|
||||
<br />
|
||||
For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file
|
||||
<br />
|
||||
|
@ -2,11 +2,9 @@ metadata:
|
||||
name: abapAddonAssemblyKitCheck
|
||||
description: This step calls AAKaaS to check the validity of the Addon Product Modelling.
|
||||
longDescription: |
|
||||
This step does the following:<ul>
|
||||
[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)
|
||||
A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)
|
||||
The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
|
||||
</ul>
|
||||
[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml).
|
||||
A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules).
|
||||
The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage in subsequent pipeline steps.
|
||||
<br />
|
||||
For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file
|
||||
<br />
|
||||
|
Loading…
Reference in New Issue
Block a user