Closed jstastny-cz closed 3 weeks ago
PR job #10
was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/10/display/redirect See console log:
PR job #11
was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/11/display/redirect See console log:
The jenkins failure is due to changes in this PR relying on DSL job generation, so should click together after merge and seed job execution.
Addressing:
1729
Problems were caused by the
githubscm.prepareCommitStatusInformation*
methods that don't resolve the fork name.To overcome this limitation, using propagation of the env variables from the PR check plugin into the jenkinsfiles of Jenkinsfile.build-and-test and Jenkinsfile.build-image .
By setting sensible defaults for the job parameters the changes should be covering both PR check and nightly build use cases.
The githubscm.checkoutIfExists method does the merging into target branch out of the box - that's why the execution differs for PR check vs nightly. In theory, we know which repo to resolve, so could be unified, but we'd need to handle the merging differently (which might be less convenient afterall).