On Mon, Sep 9, 2013 at 1:46 AM, Baptiste Mathus <[email protected]> wrote:
> OK, so I suppose you'll have to dig into the source to see if any log is
> issued, and hopefully understand what happened.
>
> My 2 cents.
Yes jenkins normally does execute the same job on the same node when
it is available, but my 2 cents is that if it matters, you are doing
something wrong or you should restrict the job to the node(s) where
you want it. Maybe there was a network glitch or something that made
jenkins think that node was unavailable.
--
Les Mikesell
[email protected]
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
