Re: How to find out WHY a job was executed on a specific slave?

2013-09-10 Thread Baptiste Mathus
Le 10 sept. 2013 07:31, Dirk Heinrichs d...@recommind.com a écrit : 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?

Re: How to find out WHY a job was executed on a specific slave?

2013-09-09 Thread Baptiste Mathus
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. Le 9 sept. 2013 07:54, Dirk Heinrichs d...@recommind.com a écrit : Am 08.09.2013 22:02, schrieb Baptiste Mathus: So, I suppose your slave was unavailable or

Re: How to find out WHY a job was executed on a specific slave?

2013-09-09 Thread Les Mikesell
On Mon, Sep 9, 2013 at 1:46 AM, Baptiste Mathus bmat...@batmat.net 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,

Re: How to find out WHY a job was executed on a specific slave?

2013-09-09 Thread Dirk Heinrichs
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...

Re: How to find out WHY a job was executed on a specific slave?

2013-09-08 Thread Baptiste Mathus
From my experience, and from what I think I've read somewhere (didn't check the code), Jenkins will indeed try to launch the build on the last slave if it's available for obvious reasons. So, I suppose your slave was unavailable or busy (did you double-check the builds that ran on it?) (see in

Re: How to find out WHY a job was executed on a specific slave?

2013-09-08 Thread Dirk Heinrichs
Am 08.09.2013 22:02, schrieb Baptiste Mathus: So, I suppose your slave was unavailable or busy (did you double-check the builds that ran on it?) Yes, I did. It was available, but idle for about 2 hours while the second build was started on another slave. Neither the master, nor the slave log

How to find out WHY a job was executed on a specific slave?

2013-09-06 Thread Dirk Heinrichs
Hi, yesterday Jenkins executed two subsequent builds of the same job on different slaves, although the slave which ran the first build was idle when the second build started. Doesn't Jenkins try to execute the next build on the same slave if possible? If yes: How do I find out why this happend?