The SAP Cloud SDK pipeline library defines essential functions for building cloud extension applications. The SAP Cloud SDK pipeline uses this library.
Apache License 2.0
27
stars
22
forks
source link
Maven task execution in checkoutAndInitLibrary #26
in the context of Cloud CI Service (CDaaS) we have encountered the following issue:
For the project [1], the Cloud SDK pipeline library tries to execute a maven task before our forked pipeline is able to insert infrastructure specific configuration.
This leads to a hanging build, because the pod for the maven tasks cannot be scheduled.
The maven task is executed here [2]. In past we have split the input stage to avoid this kind of behavior. When I understand the issue correctly, the reason why it happens for [1] is that there is a package.json and a pom.xml inside the root of the project.
If this makes sense I cannot say.
Is it possible to due the automatic versioning at a later stage?
Hi colleagues,
in the context of Cloud CI Service (CDaaS) we have encountered the following issue:
For the project [1], the Cloud SDK pipeline library tries to execute a maven task before our forked pipeline is able to insert infrastructure specific configuration. This leads to a hanging build, because the pod for the maven tasks cannot be scheduled.
The maven task is executed here [2]. In past we have split the input stage to avoid this kind of behavior. When I understand the issue correctly, the reason why it happens for [1] is that there is a
package.jsonand apom.xmlinside the root of the project. If this makes sense I cannot say.Is it possible to due the automatic versioning at a later stage?
[1] https://github.wdf.sap.corp/i069498/Costcenter-Controller-CF [2] https://github.com/SAP/cloud-s4-sdk-pipeline-lib/blob/master/vars/checkoutAndInitLibrary.groovy#L63