[JIRA] (JENKINS-44138) Add options for node launching strategy

[artem.stasuk@gmail.com (JIRA)]

Artem Stasiuk commented on JENKINS-44138

Re: Add options for node launching strategy Could you please provide a use case for such flexible configuration, this change could take some time, as current impl totally controlled by Jenkins. It defines when scale-up will be run and what amount of executors should be launched. The plugin just controls that no the max will be run. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[mark.lagendijk@connectis.nl (JIRA)]

Mark Lagendijk commented on JENKINS-44138

Re: Add options for node launching strategy

The issue is that not always when there is a queue you want to add extra nodes. With the current plugin, however, it will always scale up the nodes as soon as there is a queue. The only way to make sure this does not totally get out of control, is to limit the maximum amount of nodes. In our situation this results in two issues: There are often more nodes running then needed. There are sometimes not enough nodes, because the max is too low. Example 1 There are 5 nodes with 2 executors, all busy. There are 10 jobs in the queue. You don't want to scale up, because the 5 nodes will be able to finish everything in 10 minutes. Example 2 There are 5 nodes with 2 executors, all busy. There are 10 jobs in the queue. You do want to scale up. More nodes are needed to catch up with the queue. There are several factors that influence how you want your nodes to scale up. The startup time of new nodes + extra tasks only the first execution would do. The amount of time an average job takes to complete. The distribution of amount of jobs over time (evenly vs peaks).

Add Comment