See http://gnustep.dnsalias.org:8080/job/gnustep/67/changes
Changes:
[thebeing] Move declarations around (patch by Phillipe Roussel)
--
[...truncated 2594 lines...]
checking for cairo-ft... yes
checking CAIRO_FT_CFLAGS... -I/usr/include/cairo
Hi Greg,
I think this kind of email is what people were fearing that we would be
getting when you setup Jenkins. I identify a few issues:
On Sat, Apr 21, 2012 at 07:38:42AM -0400, greg.casame...@gmail.com wrote:
See http://gnustep.dnsalias.org:8080/job/gnustep/67/changes
Changes:
Niels,
The fact that we have had 30+ successful builds without any issues seems to
indicate a good track record with respect to Jenkins and the ci effort.
Honestly I am not going to put the messages on their own list because that
list will become a black hole and will be all too easy for people
On Sat, Apr 21, 2012 at 09:14:31AM -0400, Gregory Casamento wrote:
Niels,
The fact that we have had 30+ successful builds without any issues seems to
indicate a good track record with respect to Jenkins and the ci effort.
Honestly I am not going to put the messages on their own list because
But we haven't had a sub par experience.
Like I said, Jenkins has been in operation for about a month and many
successful builds have been run. If you're asking me to say I will 100%
guarantee that unforeseen errors may cause a problem on the server then I
can't. What I suspect is that this is
I found the issue. I accidentally changed permissions in the build
directory when I was installing something else on the server. The
problem should be corrected shortly.
My apologies to anyone who thought this was because of any instability
in a process which has been working seamlessly for
