Re: [fltk.general] Continuous integration: using Jenkins fornightly FLTK builds
Ya, I guess I'll try it with the next large checkin I do for Fl_Tree. I haven't looked at the config; I assume an anon user can't just do an SVN checkin of a spambot hidden in the Makefile so that doing an svn checkin won't run their bot? If you want, you can probably limit checkins to just us devs; you can probably just assign us login names and passwords via direct email to protect your build farm. On 04/21/12 15:30, Fabien Costantini wrote: Wow matt, I just had a quick look to the recent builds/changes that's really awesome !!! That is quickly going to be very useful, ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Continuous integration: using Jenkins fornightly FLTK builds
On 22.04.2012, at 00:34, Greg Ercolano wrote: Ya, I guess I'll try it with the next large checkin I do for Fl_Tree. I haven't looked at the config; I assume an anon user can't just do an SVN checkin of a spambot hidden in the Makefile so that doing an svn checkin won't run their bot? If you want, you can probably limit checkins to just us devs; you can probably just assign us login names and passwords via direct email to protect your build farm. It uses the svn repo on fltk.org. So, yes, you are right, fudging the Makefile would be quite harmful :-( ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
