> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpilato@collab.net]
> Sent: donderdag 1 juni 2006 5:23
> You *could* poll the server every half-hour to see if the
> youngest revision has gone up, returning a zero exit status
> if there's been a change since the last check, zero otherwise:
[..]
> So ... am I overlooking something really obvious here
> (besides the fact that either of these suggestions move you
> from a push-based system to a pull-based one)?
>
The entire goal of the buildbot is to give fast feedback on build or test
issues, a system that only checks each half-hour for updates doesn't really
serve the goal.
> But I think you'd be better off finding something that
> doesn't rely on emails as a trigger.
I got the message :)
Max Bowsher proposed on irc a combination of both approaches, that is to use
the email as the trigger to get the log from that revision (parsed from the
mail subject), then use the log detail use input to the scheduler. It gives
the info buildbot needs, while not relying on the mail format (except that
there has to be a revision in the subject).
I like that approach, probably implement it this weekend.
> I'm not opposed to adding such a hook script. Send
> suggestions to svnadmin-at-svn.collab.net.
But I don't like that :) One of the alternatives is that a hook scripts
connects over tcp to a server; sends some info concerning the change and
then that server triggers the buildbot master. I think Max's proposal is
much simpler. If requirements change in the future we can still setup an
extra hook script.
Thanks for your input.
Lieven.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 1 23:34:46 2006