On Sep 4, 2012, at 20:55 , Michael Haberler wrote: > Can I encourage you to make it less of a chore for yourself and less > blunder-prone for contributors by:
> > - documenting how a test branch can be run through the buildbot without > causing the ritual "contributor X's commit has broken the builds" emails - > obviously pushing a branch to the git.linuxcnc.org triggers a build, which I > discovered by accident - how can one make use of it properly to reduce my > red-face factor? Currently every failed build generates an email to me, and I forward the information to the dev mailing list. My intent is not to embarrass, only to inform. I've broken the build plenty of times, and made a public fool of myself in the indelible git log (see for example c7fb6a2f and the commits that follow…). I could mail the guilty developer privately instead, would that be better you think? > - it would be extra helpful to document the steps how your build environments > are set up and run, that would enable us to try this at home before pushing a > commit. I just added a page with this information (linked from the bottom of the buildbot front page): http://buildbot.linuxcnc.org/dev.html If there is any additional information that you think would be useful there, let me know and I'll add it! -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
