jamesnetherton opened a new pull request, #8737:
URL: https://github.com/apache/camel-quarkus/pull/8737

   Removes previous build steps for alternative JDK testing and introduces a 
reusable `alternate-jdk-build.yaml` workflow that accepts `jdk-version` and 
`jdk-distribution` inputs, replacing the previous monolithic approach. Thin 
caller workflows delegate to it:
   
   - `jdk21-build.yaml` — temurin 21, Sundays 14:00
   - `jdk25-build.yaml` — temurin 25, Sundays 08:00
   - `semeru17-build.yaml` — semeru 17, Saturdays 08:00
   - `semeru21-build.yaml` — semeru 21, Saturdays 14:00
   
   The old `ci-semeru-jdk.yaml` is removed. The reusable workflow detects the 
semeru distribution to skip native compilation profiles and adjust examples 
test profiles accordingly. Schedule times are spread across Saturday/Sunday 
mornings and afternoons to avoid overlap with the daily camel-master and 
quarkus-master cron builds.
   
   Also removes the `integration-tests-jvm` matrix (`['17','21']`) from all 
workflows — alternate JDK coverage is now handled by the dedicated per-version 
scheduled jobs. Path exclusion lists in `ci-build.yaml` and `pr-validate.yml` 
updated accordingly.
   
   <!-- Uncomment and fill this section if your PR is not trivial
   [ ] An issue should be filed for the change unless this is a trivial change 
(fixing a typo or similar). One issue should ideally be fixed by not more than 
one commit and the other way round, each commit should fix just one issue, 
without pulling in other changes.
   [ ] Each commit in the pull request should have a meaningful and properly 
spelled subject line and body. Copying the title of the associated issue is 
typically enough. Please include the issue number in the commit message 
prefixed by #.
   [ ] The pull request description should explain what the pull request does, 
how, and why. If the info is available in the associated issue or some other 
external document, a link is enough.
   [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close 
the named issue upon merging the pull request. Using them is typically a good 
idea.
   [ ] Please run mvn process-resources -Pformat (and amend the changes if 
necessary) before sending the pull request.
   [ ] Contributor guide is your good friend: 
https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
   -->


-- 
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]

Reply via email to