-
Improvement
-
Resolution: Fixed
-
Minor
-
None
When declaring an invalid host name we currently get the following error
Connexion à machine
ERROR: Erreur inattendue au lancement d'un esclave. Probablement un bug dans Jenkins
java.net.UnknownHostException: machine
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at java.net.InetAddress.getByName(Unknown Source)
at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:202)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:243)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
However it is a user error, not a bug in Jenkins. The exception should be caught and a user-friendly message displayed.