-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins: 1.634
ec2-plugin: 1.31
In version 1.29, I could manually provision a new slave if I was below the instance cap by clicking the button on the Manage Nodes page. In version 1.31, clicking the button takes me to the status page of an existing ec2 slave node.
- is duplicated by
-
JENKINS-33879 can't proactively scale up ec2 slaves in anticipation demand
- Resolved
-
JENKINS-33945 can't provision new nodes when a matching node is marked offline
- Closed