-
Bug
-
Resolution: Fixed
-
Minor
-
None
I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together.
When in debug, I'd noticed that "RetentionStrategy" "Demand" is testing "Computer.getDemandStartMilliseconds()" to connect the slave, but all slaves (that 'll take some time to wake up) pass in test.
Shouldn't this strategy take in account if there are executor enough and nodes starting?
I,ve made a change in RetentionStrategy that solves the problem. Anyone see any problem with this solution?
Code changed in jenkins
User: Bruno Meneguello
Path:
core/src/main/java/hudson/slaves/RetentionStrategy.java
http://jenkins-ci.org/commit/jenkins/5a32eca331bf1d5652ab908c356f0ed64de82c6f
Log:
[FIXED JENKINS-13416] On demand slave provisioning is starting all available slaves