apupier opened a new pull request, #29565:
URL: https://github.com/apache/camel/pull/29565

   # Description
   
   Due to Jenkins bug https://github.com/jenkinsci/jenkins/pull/27365, when 
Camel core builds run on alternative architecture nodes (`ppc64le` and `s390x`) 
with `throttleJobProperty(maxConcurrentPerNode: 1)`, Jenkins incorrectly 
considers idle executors on already-running nodes as available capacity. This 
prevents Jenkins from auto-provisioning new cloud nodes when a build from 
another branch is in the queue, causing jobs to wait unnecessarily for hours.
   
   This PR introduces an unthrottled helper pipeline (`Jenkinsfile.occupier`) 
and Groovy helper script (`etc/scripts/jenkins-alt-arch-nodes.groovy`) that:
   1. Queries `${JENKINS_URL}/computer/api/json` for online `ppc64le` and 
`s390x` agents.
   2. Identifies agents running a Camel build that still have idle executors.
   3. Unless the platform has already reached its maximum node limit (3 for 
`ppc64le`, 6 for `s390x`), spawns parallel 10-minute dummy sleep tasks on those 
specific nodes to occupy their idle executors.
   4. As a result, Jenkins detects zero free capacity for the architecture 
label and triggers cloud auto-provisioning for the queued build.
   
   The workaround is triggered asynchronously (`wait: false`) from the 
pre-build stage in `Jenkinsfile`, `Jenkinsfile.jdk26`, and `Jenkinsfile.jdk27`.
   
   _IBM Bob on behalf of apupier_
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (note that 
Camel 3 uses `camel-3.x`, whereas Camel 4 uses `main`)
   
   # Tracking
   - [x] If this is a bug to be solved, I have opened a JIRA issue 
(https://issues.apache.org/jira/browse/CAMEL-24290)
   
   # Apache Camel coding standards and style
   
   - [x] I checked that the files follow Camel coding standards


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