Closed rgdoliveira closed 1 year ago
PR job #1059
was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1059/display/redirect See console log:
Jenkins retest this
PR job #1060
was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1060/display/redirect See console log:
PR job
#1060
was: FAILURE Possible explanation: Pipeline failure or project build failurePlease look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1060/display/redirect See console log:
Console Logs
@rgdoliveira you need to rebase ;)
PR job #1061
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1061/display/redirect See console log:
hi, can we have a jira for this change?
have you already reported the jira @ricardozanini or we need to create a now one?
@mareknovotny @spolti we don't have a JIRA, I think @rgdoliveira identified the issue and pushed the changes based on our conversation.
@ricardozanini exactly, I created the PR based on our conversation in the channel last week. I didn't create a Jira for it because I was not sure if we would use this approach or not. So in case we agree on doing that, I can create a Jira and attach to this PR. Please, just let me know how we want to proceed.
@radtriste @rgdoliveira if we can afford to test these changes with the operator, I'm all in. So, I believe we need a JIRA/EPIC to address all the critical CVEs we have in the images.
@ricardozanini I'm not sure how this changes can be tested with the Operator? I will let @radtriste answer if he knows.
Basically the build-quarkus-app.sh
script is used to generate the maven repository zip
and the quarkus-app zip
(which is the serverless-workflow-project sample project) for both the devmode and builder images.
We need to build the images based on this PR and run a few tests with the operator using these images.
@ricardozanini hmm @radtriste can correct me if I'm wrong, but I think on the community side the devmode and builder images are built in a different way than in productization.
In community they don't use the build-quarkus-app.sh
, they actually build the maven repo zip for the images as part of the images build (like a module in the image), which is something we cannot do on prod side because OSBS doesn't allow to connect to maven central, so we have to use the build-quarkus-app.sh
to build the images maven repo zip on PNC and inject that zip when building the images on OSBS.
btw, I did a better check in the generated maven repo and it seems that using the jboss-parent actually doesn't help a lot with some old artifacts included. anyway, I will create a Jira today so we can track this and I will try a different approach to see if I can get better results.
I've created Jira https://issues.redhat.com/browse/KOGITO-9791
PR job #1063
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1063/display/redirect See console log:
@ricardozanini @radtriste @desmax74 I've built the devmode and builder images used for OSL 1.30 using a new maven repository.zip that was generated using this PR.
The images are available on docker.io and can be pulled with: $ docker pull rgdoliveira/sonata-swf-devmode-rhel8:1.30.1 $ docker pull rgdoliveira/sonata-swf-builder-rhel8:1.30.1
PR job #1064
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1064/display/redirect See console log:
@radtriste @ricardozanini could you please review? @desmax74 tested the changes with the Operator and it seems fine.
PR job #1066
was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1066/display/redirect See console log:
Jenkins retest this
PR job #1067
was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1067/display/redirect See console log:
PR job #1068
was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images/1068/display/redirect See console log:
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:
[KOGITO|RHPAM-XYZ] Subject
How to retest this PR or trigger a specific build:
- (Re)run Jenkins tests Please add comment: Jenkins [test|retest] this - Prod tests Please add comment: Jenkins (re)run [prod|Prod|PROD]How to backport a pull request to a different branch?
In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-