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

[Ivan Vučica]

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 <address@hidden> wrote:

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
address@hidden, if you guys would like me to make it just send to
the people who broke the build, that's fine.   I did a test with my
own gnu address and it bounced, so I will need to manually configure
the addresses in Jenkins for each of us.

Thanks, GC

On Sat, Mar 31, 2012 at 9:50 AM, David Chisnall <address@hidden> wrote:
> On 31 Mar 2012, at 14:48, address@hidden wrote:
>
>> See <http://192.168.1.6:8080/job/gnustep/12/>
>
> 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
>
>
>

--
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com

_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev

--
Ivan Vučica - address@hidden