[Buildbot-devel] source change for sf.net hosted CVS

[Stefan Kost]

Hi Brian,

the mail idea wont work well for sf.net hosted project as there is a sync delay 
between the developer cvs and the read only cvs. I was looking at
   http://buildbot.cvs.sourceforge.net/buildbot/buildbot/contrib/

viewcvspoll.py seems to directl access the viewcvs mysql database :(
fakechange.py from the commit-hook looks good, but then one still has to handle 
the delay and I am not sure if they have twisted installed on the sf.net cvs 
machines.

Any other ideas? I wonder if something like this could work - checking out the 
ChangeLog every e.g. 30 minutes and testing if it has been changed.

Stefan

Brian Warner wrote:
> "ensonic" <ensonic at hora-obscura.de> writes:
> 
> 
>>this might be a FAQ. How do I trigger source changes from a sf.net hosted
>>CVS. I can't install 'buildbot' there to do 'buildbot sendchange' from the
>>commithook.
> 
> 
> For sf.net, I'd suggest using email. There are a couple of ChangeSources
> which acquire mail in one way or another, and then parse them to determine
> which files were changed (by whom, with which comments, etc). The existing
> code knows how to poll a maildir for new messages, but it shouldn't be to
> hard to add others. The parsing function depends upon what code is emitting
> the mail message.. for sf.net CVS I think you'll want to use syncmail.
> 
> The usual approach is to make sure your commithook sends mail to a mailing
> list (usually named PROJECT-commits), and then subscribe your buildmaster's
> account to this list. Then each time a file is changed, everybody (including
> the buildmaster) gets email about it, and the buildmaster turns that email
> into a Change object that triggers a new build.
> 
> http://buildbot.sourceforge.net/manual-0.7.5.html#Other-mail-notification-ChangeSources
> contains some information on these sorts of change sources, but it probably
> needs to be expanded a bit.
> 
> hope that helps,
>  -Brian