-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
2.481
Jenkins 1.598
1. When taking slave offline by user - you can specify a reason.
If the slave is getting disconnected (i.e. after a reboot), the reason is changed to a java exception, and you can't see the original reason.
2. When a slave is in a "connecting" state (slave agent being lunched) and is in offline state - the reason doesn't appear on the computer page (/computer/host...).
1. Jenkins restart is one thing, after jenkins start it calls computers.updates (afair). So something can be related in this part of code.
2. probably can be related to asynchronous actions between submitted runnable in threadPoolForRemoting (afair in this way it launches slaves) and offline marking/interruption.