From 2bf0334d6d2cd1258ca892d893b287cd006b5b6a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Aur=C3=A9lien=20Pupier?= <apupier@ibm.com>
Date: Thu, 3 Sep 2026 16:55:31 +0200
Subject: [PATCH] Restore throttling of jobs per node on Jenkins
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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 <apupier@ibm.com>
---
 Jenkinsfile | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Jenkinsfile b/Jenkinsfile
index 3cfda62cc6f72..65a2da25fd845 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