This is an automated email from the ASF dual-hosted git repository.
apupier pushed a commit to branch camel-4.18.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.18.x by this push:
new 26b9a88d2337 Restore throttling of jobs per node on Jenkins
26b9a88d2337 is described below
commit 26b9a88d2337da1b3500e8f117d1170ea96b18ad
Author: Aurélien Pupier <[email protected]>
AuthorDate: Thu Sep 3 16:55:31 2026 +0200
Restore throttling of jobs per node on Jenkins
seems that an upgrade of the jenkins plugin used changed the default
value for maxConcurrentPerNode
https://github.com/jenkinsci/throttle-concurrent-builds-plugin/commit/e761815c7399ae710cf9a4023b8005fd6879d47a
, 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 <[email protected]>
---
Jenkinsfile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Jenkinsfile b/Jenkinsfile
index 3cfda62cc6f7..65a2da25fd84 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -39,7 +39,8 @@ pipeline {
throttleJobProperty(
categories: ['camel'],
throttleEnabled: true,
- throttleOption: 'category'
+ throttleOption: 'category',
+ maxConcurrentPerNode: 1
)
// This is required if you want to clean before build
