jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2025-11-06 09:09:19 +02:00
Code Issues Releases Activity

Update abapEnvironmentAddons.md: Unable to update target vectors with unchanged SWC version (#3392)

Browse Source 
* Update abapEnvironmentAddons.md

* Update documentation/docs/scenarios/abapEnvironmentAddons.md

Co-authored-by: Daniel Mieg <56156797+DanielMieg@users.noreply.github.com>

* Update abapEnvironmentAddons.md

Co-authored-by: Daniel Mieg <56156797+DanielMieg@users.noreply.github.com>
This commit is contained in:
Peter Persiel
2022-01-13 20:47:24 +01:00
committed by GitHub
parent f3b65ae43b
commit 7007efc35f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -192,9 +192,11 @@ The `version` of a software component influcences two aspects:
- The given version will be used as part of the target vector
- If there exists NO delivery package with the given version in AAKaaS the build of this package is performed
As a result, if the `addonVersion` is increased but references a software component (repository) `version` for which a delivery package has already been built no new package is built. Only a new target vector is created.
If the `version` of a software component (repository) is increased but not the `addonVersion`, a package is build but no new target vector is created, meaning the new package cannot be deployed.
If the add-on product consists of multiple software component versions (repositories), but only for one of them the `version` is increased (together with a new `commitID`), only for this software component version a new package is created. If at the same time the `addonVersion` was increased a new target Vector is created.
As a result, if the `addonVersion` is increased but references a software component (repository) `version` for which a delivery package has already been built, no new delivery package is built but only a new target vector is created. During add-on update such a target vector does not reference any new software component versions and the update of software components is skipped.
If the `version` of a software component is increased but not the `addonVersion`, a package is build but no new target vector is created, meaning the new package cannot be deployed.
If the add-on product consists of multiple software component versions, but only for one of them the `version` is increased (together with a new `commitID`), only for this software component version a new package will be created. If, at the same time, the `addonVersion` is increased a new target Vector will be created.
`branch` and `commitID` identify a specific state of a software component. Branches of a software component can include different lists of commits.
The `commitID` should only be changed while also adjusting the `version` number of a software component.