[jboss-jira] [JBoss JIRA] (SWSQE-356) Improve jenkins node provisioning scheduler

[Filip Brychta (JIRA)]

     [ https://issues.jboss.org/browse/SWSQE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Brychta resolved SWSQE-356.
---------------------------------
    Resolution: Done


Currently running jenkins with:
-Dhudson.slaves.NodeProvisioner.initialDelay=0 -Dhudson.slaves.NodeProvisioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85 -Dhudson.model.LoadStatistics.decay=0.2 -Dhudson.model.LoadStatistics.clock=5000

Delay in a queue for 20 jobs is ~1 minute which is not that bad. Longer delays were caused by https://issues.jboss.org/browse/SWSQE-360
Also found open jenkins issue which should solve this problem - https://issues.jenkins-ci.org/browse/JENKINS-24752
Some more discussion - https://github.com/jenkinsci/docker-plugin/issues/427

> Improve jenkins node provisioning scheduler
> -------------------------------------------
>
>                 Key: SWSQE-356
>                 URL: https://issues.jboss.org/browse/SWSQE-356
>             Project: Kiali QE
>          Issue Type: Sub-task
>            Reporter: Filip Brychta
>            Assignee: Filip Brychta
>
> When starting more concurrent jobs which are using the same slave labels the jobs are scheduled but stays in the queue for long time before new slave is provisioned.
> It's described here why - https://support.cloudbees.com/hc/en-us/articles/115000060512-New-Shared-Agents-Clouds-are-not-being-provisioned-for-my-jobs-in-the-queue-when-I-have-agents-that-are-suspended
> I already tried some tuning of those parameters but it still stays long in the queue.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)