[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build failed in Jenkins: gnustep #67
From: |
Niels Grewe |
Subject: |
Re: Build failed in Jenkins: gnustep #67 |
Date: |
Sat, 21 Apr 2012 15:52:48 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
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 that
> list
> will become a black hole and will be all too easy for people to ignore. The
> dev list is relatively low traffic and a little noise every once in a wild
> shouldn't present an issue.
>
> Given people's reluctance to accept Jenkins emailing the dev list I'm forced
> to
> question why some people are even contributing to this project. If you don't
> want to hear about build or test failures then I don't know what you're doing
> here.
Sorry Greg,
I think you got me all wrong. I‘m very much in favour of CI, and I
absolutely want to hear about build and test failures. What I don‘t want
is to hear about failures of the CI tool or to receive emails that are
send in response to a commit I did but require me to wade through dozens
of lines of build output in order to figure out whether I actually broke
something or if it‘s a pre-existing issue. But then again this sounds
more harsh than intended, so please take it the wrong way: I‘m merely
worried that an initial sub-par experience with Jenkins might adversely
affect people‘s opinions against an otherwise great way to ensure code
quality.
Cheers,
Niels