tkobayas opened a new issue, #7226: URL: https://github.com/apache/incubator-kie/issues/7226
PR CI jobs fail on the `ubuntu-26.04` runner image because it ships Maven 3.9.15, while the build requires Maven 3.9.16 or later. `ubuntu-latest` is being rolled out to `ubuntu-26.04`. Jobs that land on `ubuntu-24.04` still pass, so the failure depends on which image the runner gets. Example: #7224 (the failures are unrelated to the PR's changes) - [CI :: Build / ubuntu-latest, Java 17](https://github.com/apache/incubator-kie/actions/runs/39616001140/job/119277089760) - [CI :: Build / ubuntu-latest, Java 21](https://github.com/apache/incubator-kie/actions/runs/39616001140/job/119277090278) - [CI :: Examples / kogito-quarkus-examples](https://github.com/apache/incubator-kie/actions/runs/39616001151/job/119277091754), `kogito-springboot-examples`, `gradle-examples` ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.3.0:enforce (enforce-versions) on project drools-model-prototype: [ERROR] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion failed with message: [ERROR] Detected Maven Version: 3.9.15 is not in the allowed range [3.9.16,). ``` ### Cause - `kie-parent/pom.xml` sets `version.maven` = `${version.org.apache.maven}` = `3.9.16` (since #6899), and the `enforce-versions` execution uses it as the `requireMavenVersion` minimum. - `.github/workflows/ci.yaml` and `.github/workflows/pr-downstream.yml` don't set up Maven. They use whatever `mvn` the runner image provides. - In `ci.yaml`, the upstream pass runs with `-Denforcer.skip=true`, but the "Changed and affected modules" pass does not. It fails on the first affected module, so the PR's code is never compiled or tested. - In `pr-downstream.yml`, the outer build passes `-Denforcer.skip=true`, but `drools-kie-ci-with-domain-tests` runs a nested build through `maven-invoker-plugin` (`build-test-kjar`), and that build does not inherit the flag. It fails on the same image. The nested `build.log` isn't printed in the CI log, so this cause is inferred: all failing jobs ran on `ubuntu-26.04` and passing runs on `ubuntu-24.04`. ### Possible fixes 1. Install Maven 3.9.16 explicitly in the workflows: - `stCarolas/setup-maven` is on the ASF allow-list (`@*`), but it doesn't verify checksums. - Alternatively, download Maven and check its checksum manually, as the workflows already do for JBang (see the `SETUP :: Install JBang` step). This needs to work on the Linux, macOS and Windows runners in the `ci.yaml` matrix. 2. Pin `runs-on: ubuntu-24.04` as a short-term workaround. 3. Add the Maven Wrapper (`mvnw`). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
