-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.303.3, Ec2 plugin 1.66
The Jenkins EC2 plugin isn't starting existing (stopped) nodes, instead, it always starts a new one. I can see the past instances as offline in the nodes tab, but instead of starting these nodes, the plugin always starts a new instance instead.
- relates to
-
JENKINS-64520 EC2 node not start after stop/disconnect with parameter Idle termination time
-
- Open
-
[JENKINS-67190] EC2-plugin not spooling up stopped nodes, starting new nodes instead
Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Assignee | Original: FABRIZIO MANFREDI [ thoulen ] |
Link | New: This issue relates to JENKINS-64520 [ JENKINS-64520 ] |