Aurélien Pupier created CAMEL-26382:
---------------------------------------
Summary: s390x and ppc64le are not starting new jobs when one
leased node is started even if leased nodes are available
Key: CAMEL-26382
URL: https://issues.apache.org/jira/browse/CAMEL-26382
Project: Camel
Issue Type: Task
Components: build system
Affects Versions: 4.24.0
Reporter: Aurélien Pupier
this is a Jenkins bug reported
https://github.com/jenkinsci/jenkins/issues/27318 for which there is a PR
awaiting a review fro more than a month now.
Current workaround consists to launch another dummy job manually to ensure the
other leased nodes are starting.
I propose to change our Jenkins pipelines to trigger the dummy jobs
automatically and ensure the available leased nodes are started.
Consideration, it is easy when there is a single job running as just need to
start one dummy job, but in case of several we should start the same number of
already started Jenkins nodes which are not full.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
