Jenkins build is back to normal : gnustep #12

See ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev

Jenkins build is back to normal : gnustep #12

All of this defeats the purpose of the thing. I don't want to do all of this work setting jenkins up only to make it easy for people to ignore by putting it on a mailing list which has no subscribers. I would insist that, if another list is created, that all of the current maintainers subscribe t

Re: Jenkins build is back to normal : gnustep #12

On 31 Mar 2012, at 14:48, greg.casame...@gmail.com wrote: > See If you're going to spam the list with these things, could you at least use a publicly routable address? David -- Sent from my Difference Engine

Re: Jenkins build is back to normal : gnustep #12

David, If you're asking if I can make Jenkins available on a website which is accessible to the outside world, I'm not sure if I should until I configure the logins so that not just everyone can administer it. Once I have that set up I will make this public. Also, I will remove gnustep-dev@gnu.o

Re: Jenkins build is back to normal : gnustep #12

Sending a mail to the person who broke the build really is the best way to go. But please do consider opening at least the logs for viewing purposes, so the person who broke the thing (and other interested parties) can see what went wrong. :-) On Sat, Mar 31, 2012 at 16:48, Gregory Casamento wrot

Re: Jenkins build is back to normal : gnustep #12

I, honestly, would like it reported to the list so that people OTHER than the person who broke it can act on it. All too often people will ignore the email. If it is sent to the list, the maintainers as well as the person who broke it will know about it. Alternatively I could, instead of putting

Re: Jenkins build is back to normal : gnustep #12

Hi Gregory, Why not just create a new list rather than using gnustep-dev ? Cheers, Quentin. Le 31 mars 2012 à 17:12, Gregory Casamento a écrit : > I, honestly, would like it reported to the list so that people OTHER > than the person who broke it can act on it. > > All too often people will ig

Re: Jenkins build is back to normal : gnustep #12

This way, everyone will get a chance to be spammed, and everyone will get a chance to ignore the mail. I don't think you'll get the effect you're aiming for. It's better if just the person who broke the thing got the mail, and if others could occasionally check the build logs to see if anything is

Re: Jenkins build is back to normal : gnustep #12

Actually, that's a good idea as well. :) On Sat, Mar 31, 2012 at 12:15 PM, Jordan Schidlowsky wrote: > Ya, I'll probably unsubscribe if I get broken build emails…  Pls create > another list. > > On 2012-03-31, at 9:46 AM, Ivan Vučica wrote: > > This way, everyone will get a chance to be spammed,

Re: Jenkins build is back to normal : gnustep #12

Ya, I'll probably unsubscribe if I get broken build emails… Pls create another list. On 2012-03-31, at 9:46 AM, Ivan Vučica wrote: > This way, everyone will get a chance to be spammed, and everyone will get a > chance to ignore the mail. I don't think you'll get the effect you're aiming > for

Re: Jenkins build is back to normal : gnustep #12

Hi Greg, Am 01.04.2012 um 02:27 schrieb Gregory Casamento: > All of this defeats the purpose of the thing. I don't want to do all of this > work setting jenkins up only to make it easy for people to ignore by putting > it on a mailing list which has no subscribers. > > I would insist that, if

Re: Jenkins build is back to normal : gnustep #12

Hi guys, Am 01.04.2012 08:37, schrieb Dr. H. Nikolaus Schaller: > Hi Greg, > > Am 01.04.2012 um 02:27 schrieb Gregory Casamento: > >> All of this defeats the purpose of the thing. I don't want to do all of >> this work setting jenkins up only to make it easy for people to ignore by >> putting

Re: Jenkins build is back to normal : gnustep #12

Hi, On 2012-04-01 10:11:37 +0200 Niels Grewe wrote: I see that you want to create a feedback loop, which is IMHO a very good means to stabilize the code quality. +1 I think it's an applaudable effort that Greg is taking here. +1 for me too But I'd also like to call some attention to a