是否有可能让 Jenkins 更快地从附加云中创建工人？
Is it possible to make Jenkins create workers from attached clouds faster?
我有一个使用 mesos plugin 的 Jenkins 实例。几乎我所有的工作都是通过 Mesos 任务触发的。我想让 worker 生成更积极一些。
当前的问题是，对于 mesos 插件，我有所有作业将 mesos 任务标记为一次性使用从属，当构建在这些从属之一上进行时，Jenkins 强制任何排队的作业到等待这些奴隶的潜在执行者，而不是启动新实例。
根据日志，Jenkins 似乎还有一个计时器，该计时器定期检查是否应根据排队作业的数量/超额工作量启动任何从站。是否可以减少该进程的轮询间隔？
来自Mesos Jenkins Plugin Readme: over provisioning flags
By default, Jenkins spawns slaves conservatively. Say, if there are 2 builds in queue, it won't spawn 2 executors immediately. It will spawn one executor and wait for sometime for the first executor to be freed before deciding to spawn the second executor. Jenkins makes sure every executor it spawns is utilized to the maximum. If you want to override this behavior and spawn an executor for each build in queue immediately without waiting, you can use these flags during Jenkins startup:
-Dhudson.slaves.NodeProvisioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
我有一个使用 mesos plugin 的 Jenkins 实例。几乎我所有的工作都是通过 Mesos 任务触发的。我想让 worker 生成更积极一些。
当前的问题是，对于 mesos 插件，我有所有作业将 mesos 任务标记为一次性使用从属，当构建在这些从属之一上进行时，Jenkins 强制任何排队的作业到等待这些奴隶的潜在执行者，而不是启动新实例。
根据日志，Jenkins 似乎还有一个计时器，该计时器定期检查是否应根据排队作业的数量/超额工作量启动任何从站。是否可以减少该进程的轮询间隔？
来自Mesos Jenkins Plugin Readme: over provisioning flags
By default, Jenkins spawns slaves conservatively. Say, if there are 2 builds in queue, it won't spawn 2 executors immediately. It will spawn one executor and wait for sometime for the first executor to be freed before deciding to spawn the second executor. Jenkins makes sure every executor it spawns is utilized to the maximum. If you want to override this behavior and spawn an executor for each build in queue immediately without waiting, you can use these flags during Jenkins startup:
-Dhudson.slaves.NodeProvisioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85