apupier opened a new pull request, #28273:
URL: https://github.com/apache/camel/pull/28273
The current load on GitHub Actions at Apache org level is currently very
high causing several hours of queued jobs.
Given that we improved the speed and stability of the build on Jenkins
drastically recently, we hope that we can afford to take the risk to not test
with JDK 25 on all PRs.
JDK 25 can still be triggered on demand via workflow_dispatch by passing the
new 'include_jdk25' boolean input. This runs a separate 'build-jdk25'
job (continue-on-error: true) that is otherwise identical to the main build
job. Because workflow_dispatch runs are not associated with a PR check, a JDK
25 failure will never block merging — it is purely informational. Only
maintainers with write access to apache/camel can trigger the on-demand run:
gh workflow run "Build and test" \
--repo apache/camel \
-f pr_number=XXXX \
-f pr_ref=refs/pull/XXXX/head \
-f include_jdk25=true
Alternatively, use the GitHub web UI: Actions → Build and test → Run
workflow → check "Also run the build on JDK 25 (experimental)".
Co-authored-by: IBM Bob 2.2.1
# Description
<!--
- Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
-->
# Target
- [ ] I checked that the commit is targeting the correct branch (Camel 4
uses the `main` branch)
# Tracking
- [ ] If this is a large change, bug fix, or code improvement, I checked
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for
the change (usually before you start working on it).
<!--
# *Note*: trivial changes like, typos, minor documentation fixes and other
small items do not require a JIRA issue. In this case your pull request should
address just this issue, without pulling in other changes.
-->
# Apache Camel coding standards and style
- [ ] I checked that each commit in the pull request has a meaningful
subject line and body.
<!--
If you're unsure, you can format the pull request title like `[CAMEL-XXX]
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the
appropriate JIRA issue.
-->
- [ ] I have run `mvn clean install -DskipTests` locally from root folder
and I have committed all auto-generated changes.
<!--
You can run the aforementioned command in your module so that the build
auto-formats your code. This will also be verified as part of the checks and
your PR may be rejected if if there are uncommited changes after running `mvn
clean install -DskipTests`.
You can learn more about the contribution guidelines at
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
-->
# AI-assisted contributions
- [ ] If this PR includes AI-generated code, commits have proper
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR
description identifies the AI tool used.
--
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]
