When running jobs that depend on a on-demand slave it takes 1-2 minutes before Jenkins decides to try and start the node. This is irritating when running small jobs that takes less time to complete than Jenkins takes to decide to bring up a node.
Originally reported by ealbgus, imported from: Improve start up time of on-demand slaves when no executors is available
- status: Resolved
- priority: Minor
- component(s): core
- label(s): jenkins, slave
- resolution: Fixed
- resolved: 2024-06-18T15:30:37+00:00
- votes: 1
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
When running jobs that depend on a on-demand slave it takes 1-2 minutes before Jenkins decides to try and start the node. This is irritating when running small jobs that takes less time to complete than Jenkins takes to decide to bring up a node.
- environment:
Jenkins 1.466.1 on Linux
When running jobs that depend on a on-demand slave it takes 1-2 minutes before Jenkins decides to try and start the node. This is irritating when running small jobs that takes less time to complete than Jenkins takes to decide to bring up a node.
Originally reported by ealbgus, imported from: Improve start up time of on-demand slaves when no executors is available
Raw content of original issue
Jenkins 1.466.1 on Linux