Re: Jenkins set up for GNUstep...

[Fred Kiefer]

Could you please explain how this setup compares to the old nightly 
build system that Adam used to provide? The benefit there was that it 
allowed multiple machines to register as build hosts. Normally the build 
works fine on the machine of the submitter, we need completely different 
setups to detect the problems with submits.
It would be just great if there were an easy way to move over the old 
distributed build farm to the new system.

Running the tests on your machine is surely fine, but sending out mails 
on failed tests may be a bit annoying. In gui we have a few tests that 
are known failures. I am going to mark all of the as "dashed hopes" for 
now. The problem here is that we want to encourage people to write more 
test code, if a failed test ends up with a mail to everybody this may 
not send the right message.

Fred

On 28.03.2012 14:57, Gregory Casamento wrote:
> It shouldnt.  It should be on a relatively high traffic list, since its
> important that the messages be recieved.
>
> No failed builds yet. ;). Im going to add the unit tests today.
>
> GC
>
> On Wednesday, March 28, 2012, Ivan Vučica<address@hidden>  wrote:
> > Let's hope it doesn't end up spamming everyone tracking -dev ;)
> >
> > If it does, it may make sense to send those mails to a separate mailing
> list.
> > On Wed, Mar 28, 2012 at 07:43, Gregory Casamento<address@hidden>
> wrote:
> > > Hey guys,
> > >
> > > I have set up a local Jenkins instance which builds GNUstep whenever
> > > there is a change.
> > >
> > > I have configured it to email the address@hidden list whenever
> > > the build is broken.  Currently it is only configured to run the build
> > > itself, but I plan on adding the unit tests as well.   This way we can
> > > see immediately when the build is broken or when one of the tests is
> > > broken.