[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: mailer.py on svn.collab.net

From: Ben Reser <ben_at_reser.org>
Date: 2006-06-05 11:29:02 CEST

On 5/31/06, Lieven Govaerts <lgo@mobsol.be> wrote:
> I'm using the commit mails sent to svn@subversion.tigris.org to trigger the
> buildbot master. It parses those mails to get branch, author, filestamp,
> revision, changed files and log message of the committed change. With this
> information it determines wether or not to trigger the buildslave, and to
> instruct them to update and build their working copies.
> Based on the content and a comment from maxb on irc I now know that those
> mails were only meant for human consumption, so I shouldn't use them with th
> buildbot. But I'm currently lacking an alternative.

Why not just use the emails to trigger a script that polls the server
looking for new commits since the last time it ran. Just track the
last commit you processed then run a log from last_rev+1:HEAD. Get
the data you need that way. Then you're entirely not depedent upon a
format and even if say the email notification system should get broken
for a short time your build bot would eventually catch up with all the
old work.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 5 11:29:30 2006

This is an archived mail posted to the Subversion Dev mailing list.