On 22.04.2012, at 04:07, Greg Ercolano wrote:
You could probably passwd protect the job trigger, or
put it in the dev menu (which lets us trigger website updates),
or maybe you already have -- I haven't really looked into this
yet, my mind elsewhere at the moment.
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 :-(
But it is
On 22.04.2012, at 00:56, Fabien Costantini wrote:
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 =
On 04/21/12 15:44, Matthias Melcher wrote:
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
4 matches
Mail list logo
