[Buildbot-devel] Perforce (P4) commit trigger

[Scott Lamb]

On Sep 12, 2006, at 10:39 AM, Brian Warner wrote:
> For your particular purposes, the P4Poller is probably more  
> appropriate, but
> I mention sendchange because a lot of other version-control systems  
> offer
> some kind of commit hook that lets you run a shell command, and for  
> those
> systems 'buildbot sendchange' may be the easiest way to wire it up  
> to the
> buildmaster.

Actually, Perforce does, too. That's the triggers mechanism. [1] But  
you'd still have to do significant parsing on the "p4 changes" output  
to get even the branch name, since Perforce's model is all file- 
based. That's why I mention using code from P4Poller.

[1] - http://www.perforce.com/perforce/doc.061/manuals/p4sag/ 
06_scripting.html#1057726

-- 
Scott Lamb <http://www.slamb.org/>