On Wed, Nov 25, 2009 at 4:45 PM, Marcus Meissner <mar...@jet.franken.de> wrote: > On Wed, Nov 25, 2009 at 05:21:30PM -0500, Steven Edwards wrote: >> On Wed, Nov 25, 2009 at 12:08 PM, Austin English >> <austinengl...@gmail.com> wrote: >> > The other neat thing is that it will run git fetch in a loop every 30 >> > minutes (again, overridable), so that you can run it in the morning >> > while waiting for AJ to commit. Once commits are made to the git >> > master branch (but not stable), the script will kick into motion. >> >> It would be nice to dummy email account subscribed to the commit >> messages that it could poll to trigger the checkout, build, test >> cycle. >> >> To make a Continuous Integration Service around it it should run as a >> background process under another user out of init in a Xnest/VNC >> session. I am thinking something like a winecis user which would run >> these scripts, fetch and the Xnest session as a service we could call >> winecis. >> >> I did something similar recently for a stupid java service that had to >> have an interactive gui. > > As AJ is pushing just once a day you can also run your fetch script > once a day... Perhaps triggered by a commit mail.
Sure, that would be an option if the system has e-mail configured, but since I use webmail, I went with the 'sit and wait' method. For other projects that script would obviously need a different strategy (though I don't other projects are running winetest.exe daily ;-)). -- -Austin