On Tue, Mar 19, 2013 at 2:55 PM, Rafael Antognolli <[email protected]> wrote: > Same here, the messages don't bother me at all. > > +1 for the old messages and colors (as long as it's R, G or B) > > On Tue, Mar 19, 2013 at 2:49 PM, Michael Blumenkrantz > <[email protected]> wrote: >> On Tue, 19 Mar 2013 17:43:41 +0000 >> Daniel Willmann <[email protected]> wrote: >> >>> Hello, >>> >>> as you know we have had Jenkins running and reporting build issues for >>> almost two weeks now. After initial hiccups I think it has performed >>> quite well so far. I know of only one occasion where Jenkins blamed the >>> wrong commit for failing (and that was only because the segfault didn't >>> happen every time the tests ran) and I think it is worth having the >>> Jenkins bot report failed and fixed builds. >>> >>> All was fine until earlier today when the Jenkins bot got kicked from >>> #edevelop for use of colors and excessive messaging. I disabled colors >>> and reduced the message to only report success of failure in order to >>> have the bot in the channel again. >>> >>> I do think, however, that the earlier options were useful and we should >>> re-enable them - thus this mail. >>> >>> What the bot actually printed was this: >>> >>> <efl-jenkins> Yippie, build fixed! >>> <efl-jenkins> Project efl build #116:FIXED in 14 min: >>> http://jenkins.enlightenment.org/job/efl/116/ >>> <efl-jenkins> * tom: Disable cow magic in dev profile, instead of a hack >>> in the source. >>> <efl-jenkins> * tom: Eina cow: Don't tests things that depend on magic >>> when it's off. >>> >>> When enabling colors the bot writes the status SUCCESS/FAILURE in >>> green/red. This allows me to quickly look for the latest status in the >>> backlog which I find quite useful. It will also highlight commit >>> messages containing the word "test" in magenta. >>> >>> The other option I disabled was to also include the changes that >>> contributed towards this status change (the last two messages). This has >>> the advantage of highlighting whoever broke the build (or fixed it) and >>> gives you a rough idea what could have broken it. >>> >>> So what do you think? Is this too much, does it bother you? Should we >>> re-enable the these features? >>> >>> >>> Regards, >>> Daniel >>> >> >> Your reasoning for enabling the currently-disabled features is well-worded >> and without flaw, and I hardly think seeing an extra line or some colors >> when Cedric breaks build will ruin anyone's day more than it already has >> been. >> >> I cast two votes for putting it back the way it was.
+2 >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_mar >> _______________________________________________ >> enlightenment-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > Rafael Antognolli > http://antognolli.org/ > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Bruno Dilly Lead Developer ProFUSION embedded systems http://profusion.mobi ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
