Am 09.09.2013 17:03, schrieb Les Mikesell:
> Maybe there was a network glitch or something that made
> jenkins think that node was unavailable.
Yes, see subject. This is exactly what I want to find out. The question
is: How? Is there any Jenkins log file that says: "Couldn't use slave X,
because... Using slave Y instead."
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Infrastructure
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 1596666 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
