www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Lehmkühler" <andr...@lehmi.de>
Subject RE: Jenkins builds not triggering?
Date Tue, 07 May 2013 11:49:01 GMT

Hi,

"Andreas Lehmkühler" <andreas@lehmi.de> hat am 7. Mai 2013 um 12:18 geschrieben:
> Hi,
>
>
> Gavin McDonald <gavin@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

Mime
View raw message