Closed nmirasch closed 9 months ago
nmirasch
commented
11 months ago What have been added in this PR is to share the same code to do the calls to the jobs REST endpoints to perform Cancel and Rescheduling between the Dataindex addons and Dataindex standalone working modes.
@wmedvede @fjtirado @pefernan Could you take a look?
kie-ci3
commented
11 months ago PR job #1 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/1/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
11 months ago PR job #2 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/2/display/redirect
Test results:
Those are the test failures:
jstastny-cz
commented
11 months ago I've deleted a comment from PR check that was triggered by accident from my temporary pipeline tests, left only the relevant results here.
kie-ci3
commented
11 months ago PR job #3 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/3/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
10 months ago PR job #4 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/4/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
10 months ago PR job #5 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/5/display/redirect
Test results:
Those are the test failures:
nmirasch
commented
10 months ago @jstastny-cz @wmedvede @pefernan finally this PR has the green, could you please review? Thanks in advanced!
kie-ci3
commented
10 months ago PR job #7 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/7/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
10 months ago PR job #1 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/temporary/job/kogito-apps-1.40.x-pr/job/PR-1894/1/display/redirect
Test results:
Those are the test failures:
nmirasch
commented
10 months ago Jenkins retest this
nmirasch
commented
10 months ago Jenkins retest this
kie-ci3
commented
10 months ago PR job #10 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/10/display/redirect
Test results:
Those are the test failures:
sonarcloud[bot]
commented
10 months ago SonarCloud Quality Gate failed. 
0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells
No Coverage information
3.4% Duplication
Catch issues before they fail your Quality Gate with our IDE extension 
SonarLint
kie-ci3
commented
10 months ago PR job #15 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/15/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
10 months ago PR job #19 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/19/display/redirect
Test results:
Those are the test failures:
kie-ci3
commented
10 months ago PR job #24 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1894/24/display/redirect
Test results:
Those are the test failures:
nmirasch
commented
10 months ago Jenkins retest this
… with job service jira: https://issues.redhat.com/browse/KOGITO-8841 Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject[0.9.x] KOGITO-XYZ SubjectHow to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use [build-chain tool](https://github.com/kiegroup/github-action-build-chain) to handle cross repository builds and be sure that we always use latest version of the code for each repository. [build-chain tool](https://github.com/kiegroup/github-action-build-chain) is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See [local execution](https://github.com/kiegroup/github-action-build-chain#local-execution) details to get more information about it.How to retest this PR or trigger a specific build:
- for pull request checks Please add comment: Jenkins retest this - for a specific pull request check Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] tests - for quarkus branch checks Run checks against Quarkus current used branch Please add comment: Jenkins run quarkus-branch - for a quarkus branch specific check Run checks against Quarkus current used branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-branch - for quarkus main checks Run checks against Quarkus main branch Please add comment: Jenkins run quarkus-main - for a specific quarkus main check Run checks against Quarkus main branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-main - for quarkus lts checks Run checks against Quarkus lts branch Please add comment: Jenkins run quarkus-lts - for a specific quarkus lts check Run checks against Quarkus lts branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-lts - for native checks Run native checks Please add comment: Jenkins run native - for a specific native check Run native checks Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native - for native lts checks Run native checks against quarkus lts branch Please add comment: Jenkins run native-lts - for a specific native lts check Run native checks against quarkus lts branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native-ltsHow 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-Quarkus-3 PR check is failing ... what to do ?
The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`. The first patch, called `0001_before_sh.patch`, is generated from Openrewrite `.ci/environments/quarkus-3/quarkus3.yml` recipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch. No panic, there is an easy way to regenerate it. You just need to comment on the PR: ``` jenkins rewrite quarkus-3 ``` and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated. Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.