[4.22.x] Restore throttling of jobs per node on Jenkins - #26095
Merged
apupier merged 1 commit intoSep 4, 2026
Conversation
apupier
marked this pull request as ready for review
September 3, 2026 15:14
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
5 tasks
gnodet
reviewed
Sep 3, 2026
gnodet
left a comment
gnodet
left a comment
Contributor
There was a problem hiding this comment.
Correct backport of #26094 to camel-4.22.x. The change is identical — explicitly restoring maxConcurrentPerNode: 1 after the throttle plugin default change.
Same nit as on the main PR: trailing blank line in Jenkinsfile that Jenkinsfile.jdk26 doesn't have.
This review was generated by an automated reviewer (Hermès) on behalf of @gnodet.
| categories: ['camel'], | ||
| throttleEnabled: true, | ||
| throttleOption: 'category' | ||
| throttleOption: 'category', |
Contributor
There was a problem hiding this comment.
Nit: trailing blank line. Jenkinsfile.jdk26 doesn't have it.
Suggested change
| throttleOption: 'category', | |
| maxConcurrentPerNode: 1 |
seems that an upgrade of the jenkins plugin used changed the default value for maxConcurrentPerNode jenkinsci/throttle-concurrent-builds-plugin@e761815 , so with this relase https://github.com/jenkinsci/throttle-concurrent-builds-plugin/releases/tag/624.vc427fa_e0e503 When no value set previously, it was considering a value of one. we are still not ready for playing the tests in //, there are still port conflicts and artifacts could overwrite them in the local repository causing wrong testing. Signed-off-by: Aurélien Pupier <apupier@ibm.com>
apupier
force-pushed
the
camel-4.22.x-backportJenkinsThrottling
branch
from
September 3, 2026 15:54
587217f to
4e0e7e4
Compare
oscerd
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
seems that an upgrade of the jenkins plugin used changed the default value for maxConcurrentPerNode
jenkinsci/throttle-concurrent-builds-plugin@e761815 , so with this relase
https://github.com/jenkinsci/throttle-concurrent-builds-plugin/releases/tag/624.vc427fa_e0e503
When no value set previously, it was considering a value of one.
we are still not ready for playing the tests in //, there are still port conflicts and artifacts could overwrite them in the local repository causing wrong testing.
Description
Target
mainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally from root folder and I have committed all auto-generated changes.AI-assisted contributions
Co-authored-bytrailers) and the PR description identifies the AI tool used.