You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Robbie Gemmell <ro...@gmail.com> on 2013/05/06 12:10:42 UTC

Jenkins builds not triggering?

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

Re: Jenkins builds not triggering?

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

I can confirm that for the "sis-jdk7" and "sis-trunk" for instance, the 
jobs are not trigged since May 3th. Manual trigs work well, except for 
the solaris1 node which seems to be out of space.

     Regards,

         Martin


Le 06/05/13 12:41, Olivier Lamy a écrit :
> which jobs ?
>
> 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
>> 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
>
>

Re: Jenkins builds not triggering?

Posted by Andreas Lehmkühler <an...@lehmi.de>.

Hi,

sorry for jumping in, we have the same issue with our PDFBox build [1]. I've
triggered the last build on solaris1 manually and everything works fine. But
the automatic trigger doesn't work. According to th scmPollLog [2] the last
jenkins poll is 4 days ago.

BR
Andreas Lehmkühler

[1] https://builds.apache.org/job/PDFBox-trunk/
[2] https://builds.apache.org/job/PDFBox-trunk/scmPollLog/

Olivier Lamy <ol...@apache.org> hat am 6. Mai 2013 um 12:41 geschrieben:
> which jobs ?
>
> 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
> > 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

RE: Jenkins builds not triggering?

Posted by Andreas Lehmkühler <an...@lehmi.de>.

Hi,

"Andreas Lehmkühler" <an...@lehmi.de> hat am 7. Mai 2013 um 12:18 geschrieben:
> Hi,
>
>
> Gavin McDonald <ga...@16degrees.com.au> hat am 7. Mai 2013 um 12:06
> geschrieben:
> >
> >
> > > -----Original Message-----
> > > From: Andreas Lehmkuehler [mailto:andreas@lehmi.de]
> > > Sent: Tuesday, 7 May 2013 2:55 PM
> > > To: builds@apache.org
> > > Subject: Re: Jenkins builds not triggering?
> > >
> > > Hi,
> > >
> > > Am 07.05.2013 02:24, schrieb Gavin McDonald:
> > > > I've restarted the Jenkins master, let's see what that does.
> > > Thanks Gav, that did the trick, the trigger now works fine ..... but the
> > solaris
> > > slave ran out of disc space again [1]
> >
> > well, it never has ran out of disk space, there's over 160GB free now.
> > I need to find the real reason.
> I guess there was a misunderstanding. According to Jukkas comment in another
> thread (Re: Jackrabbit-trunk - Build # 2116 - St ill Failing ), the slave
> doesn't
> run out of disc space but memory. The error message "Not enough space" is IMHO
> a little bit misleading. Maybe it is sufficient to increase some of the maven
> memory options, probably the memory settings of the slave are the problem.
I've applied the maven params as suggested by Jukka and the last (manually
triggered)
build works fine. Let's see if this is the solution or if it just works by a
fluke.

>
> > Gav...
>
> BR
> Andreas Lehmkühler

BR
Andreas Lehmkühler

RE: Jenkins builds not triggering?

Posted by Andreas Lehmkühler <an...@lehmi.de>.

Hi,


Gavin McDonald <ga...@16degrees.com.au> hat am 7. Mai 2013 um 12:06 geschrieben:
>
>
> > -----Original Message-----
> > From: Andreas Lehmkuehler [mailto:andreas@lehmi.de]
> > Sent: Tuesday, 7 May 2013 2:55 PM
> > To: builds@apache.org
> > Subject: Re: Jenkins builds not triggering?
> >
> > Hi,
> >
> > Am 07.05.2013 02:24, schrieb Gavin McDonald:
> > > I've restarted the Jenkins master, let's see what that does.
> > Thanks Gav, that did the trick, the trigger now works fine ..... but the
> solaris
> > slave ran out of disc space again [1]
>
> well, it never has ran out of disk space, there's over 160GB free now.
> I need to find the real reason.
I guess there was a misunderstanding. According to Jukkas comment in another
thread (Re: Jackrabbit-trunk - Build # 2116 - St ill Failing ), the slave
doesn't
run out of disc space but memory. The error message "Not enough space" is IMHO
a little bit misleading. Maybe it is sufficient to increase some of the maven
memory options, probably the memory settings of the slave are the problem.

> Gav...

BR
Andreas Lehmkühler

RE: Jenkins builds not triggering?

Posted by Gavin McDonald <ga...@16degrees.com.au>.


> -----Original Message-----
> From: Andreas Lehmkuehler [mailto:andreas@lehmi.de]
> Sent: Tuesday, 7 May 2013 2:55 PM
> To: builds@apache.org
> Subject: Re: Jenkins builds not triggering?
> 
> Hi,
> 
> Am 07.05.2013 02:24, schrieb Gavin McDonald:
> > I've restarted the Jenkins master, let's see what that does.
> Thanks Gav, that did the trick, the trigger now works fine ..... but the
solaris
> slave ran out of disc space again [1]

well, it never has ran out of disk space, there's over 160GB free now.
I need to find the real reason.

Gav...

> 
> > Gav...
> 
> BR
> Andreas Lehmkühler
> 
> [1] https://builds.apache.org/job/PDFBox-trunk/648/console
> 
> >> -----Original Message-----
> >> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
> >> Sent: Monday, 6 May 2013 9:05 PM
> >> To: builds@apache.org
> >> Subject: Re: Jenkins builds not triggering?
> >>
> >> 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 <ol...@apache.org> wrote:
> >>
> >>> which jobs ?
> >>>
> >>> 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
> >>>> 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
> >>>
> >

Re: Jenkins builds not triggering?

Posted by Andreas Lehmkuehler <an...@lehmi.de>.

Hi,

Am 07.05.2013 02:24, schrieb Gavin McDonald:
> I've restarted the Jenkins master, let's see what that does.
Thanks Gav, that did the trick, the trigger now works fine ..... but the solaris
slave ran out of disc space again [1]

> Gav...

BR
Andreas Lehmkühler

[1] https://builds.apache.org/job/PDFBox-trunk/648/console

>> -----Original Message-----
>> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
>> Sent: Monday, 6 May 2013 9:05 PM
>> To: builds@apache.org
>> Subject: Re: Jenkins builds not triggering?
>>
>> 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 <ol...@apache.org> wrote:
>>
>>> which jobs ?
>>>
>>> 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
>>>> 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
>>>
>

RE: Jenkins builds not triggering?

Posted by Gavin McDonald <ga...@16degrees.com.au>.

I've restarted the Jenkins master, let's see what that does.

Gav...


> -----Original Message-----
> From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
> Sent: Monday, 6 May 2013 9:05 PM
> To: builds@apache.org
> Subject: Re: Jenkins builds not triggering?
> 
> 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 <ol...@apache.org> wrote:
> 
> > which jobs ?
> >
> > 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
> > > 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
> >

Re: Jenkins builds not triggering?

Posted by Robbie Gemmell <ro...@gmail.com>.

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 <ol...@apache.org> wrote:

> which jobs ?
>
> 2013/5/6 Robbie Gemmell <ro...@gmail.com>:
> > 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
>

Re: Jenkins builds not triggering?

Posted by Olivier Lamy <ol...@apache.org>.

which jobs ?

2013/5/6 Robbie Gemmell <ro...@gmail.com>:
> 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