Re: [fltk.general] Continuous integration: using Jenkins fornightlyFLTK builds
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 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 :-( Ah, OK, I saw something about 'anon' in your first post, so I thought maybe anonymous had access. If you're pulling the fltk.org trunk and building it, that sounds safe enough, since it's just the devs that have write access. And an anon trigger of a job probably isn't a bad thing, since the stuff the job runs is fixed and not world writable. 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. But when I do my big checkin, I'll look forward to a cross platform build; I'm always bad about windows, cause I hate the damn IDE. Not crazy about the OS either.. I keep that box off mostly. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Continuous integration: using JenkinsfornightlyFLTK builds
> Yes. I have to trust all developers that there is nothing nasty checked = > in. And I must read the SVN logs.= > Also, at least on all my macs + linux boxes ; I know that a potentially nasty checkin could only harm my devl (user) local account, isn't it the case on your machines ? I guess there is no need to run a sudo make install for nightly builds purpose (though it could also be useful but probably not a good idea to authorize that) ? ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Continuous integration: using Jenkins fornightlyFLTK builds
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 = >> Makefile would be quite harmful :-( > But it is already limited to devs to check in changes in the svn repo on > fltk.org right ? > So checkins are 'already' limited, aren't they ? Yes. I have to trust all developers that there is nothing nasty checked in. And I must read the SVN logs. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Continuous integration: using Jenkins fornightlyFLTK builds
> > 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 already limited to devs to check in changes in the svn repo on fltk.org right ? So checkins are 'already' limited, aren't they ? ___ 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
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 for nightly FLTK builds
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, -Fabien From: Matthias Melcher To: Mirror fltk.general Newsgroup of Sent: Saturday, April 21, 2012 4:39:04 PM Subject: [fltk.general] Continuous integration: using Jenkins for nightly FLTK builds Hi guys, as announced earlier, I have spent a bunch of TV dinners with Jenkins to set up a build farm. Here is the link: http://matthiasm.mooo.com/jenkins (let me kno if this does not work) The build farm is set up from three machines that I had laying around. The server is an Ubuntu system on an AMD 64 box. It runs a web server and Jenkins, and also compiles FLTK 1.3 form the command line. It's an old Siemens desktop machine that I scavenged it the local IRS offices (but it did not have my neighbor's tax return on it anymore ;-). The second machine is some bare bones Vista P.O.S. that is so slow that it has issues even opening the Windows menu. Well, I am in no hurry, so it now has to suffer under the high demands of VisualC 2010. There is no MinGW setup and job on this machine yet. The third machine is an old MacBook with a dual core Intel running the current version of Xcode. There is no command line job on this machine yet. All jobs check the SVN repository at a random time during the night (CET), but it is also possible for anonymous users to launch any job from the web interface. Suggestions welcome. - Matthias PS: Jenkins adds all names from SVN commits to the People list - just in case you were wondering... ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
[fltk.general] Continuous integration: using Jenkins for nightly FLTK builds
Hi guys, as announced earlier, I have spent a bunch of TV dinners with Jenkins to set up a build farm. Here is the link: http://matthiasm.mooo.com/jenkins (let me kno if this does not work) The build farm is set up from three machines that I had laying around. The server is an Ubuntu system on an AMD 64 box. It runs a web server and Jenkins, and also compiles FLTK 1.3 form the command line. It's an old Siemens desktop machine that I scavenged it the local IRS offices (but it did not have my neighbor's tax return on it anymore ;-). The second machine is some bare bones Vista P.O.S. that is so slow that it has issues even opening the Windows menu. Well, I am in no hurry, so it now has to suffer under the high demands of VisualC 2010. There is no MinGW setup and job on this machine yet. The third machine is an old MacBook with a dual core Intel running the current version of Xcode. There is no command line job on this machine yet. All jobs check the SVN repository at a random time during the night (CET), but it is also possible for anonymous users to launch any job from the web interface. Suggestions welcome. - Matthias PS: Jenkins adds all names from SVN commits to the People list - just in case you were wondering... ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
