-
Bug
-
Resolution: Fixed
-
Minor
Currently, an exception thrown in SlaveComputer.setNode() prevents Jenkins from starting (JENKINS-38389).
It would be nice to catch RuntimeException there for robustness, as advised by jglick there.
- relates to
-
JENKINS-38389 jenkins restart fails after installing ec2 plugin
-
- Closed
-
- links to
[JENKINS-42043] A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Link |
New:
This issue relates to |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Labels | Original: robustness | New: newbie-friendly robustness |
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Andrew Bayer [ abayer ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
But what should happen if the operation fails?
The stacktrace shows that Jenkins is currently updating all "computers" to see which ones to reuse/what executors to remove. If the node failed to update should it then be considered for reuse or for removal?
The error in ec2 plugin suggests that it was a "harmless" mistake and we should probably keep it around, while I would guess in most cases since it is in error it should be removed from the list.