Hi Olivier, As mentioned, given that there are no jobs executing at all right now from any project it seems like it might be something affecting all the jobs. That said, as far as the ones I help look after...
An example of a nightly time triggered job that has only run since May 2nd when it was manually started by me: https://builds.apache.org/job/Qpid-Java-Artefact-Release/ An example of a svn change triggered build that has not run since May 2nd despite numerous commits that should have triggered it: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.7/ Robbie On 6 May 2013 11:41, Olivier Lamy <[email protected]> wrote: > which jobs ? > > 2013/5/6 Robbie Gemmell <[email protected]>: > > Hi, > > > > I noticed yesterday that some Jenkins jobs I would have exected to run > (due > > to time and/or svn change triggers) in the previous day or two hadn't > done > > so, not because they were waiting in a queue but because they simply > hadn't > > been tiggered at all. Requesting a build for the jobs manually worked and > > they completely successfully. > > > > The same thing looks to be happening still and there are no jobs from any > > project actually executing on the nodes right now, suggesting it isn't > just > > the jobs that I was interested in that are affected. Could someone take a > > look? > > > > Thanks, > > Robbie > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy >
