[Buildbot-devel] Perforce (P4) commit trigger

Ben Hearsum bjhearsu at learn.senecac.on.ca
Thu Aug 31 12:50:10 UTC 2006


I haven't used the P4 modules before, but I believe you would use the
P4Source module along with a Scheduler. The P4Source would submit
changes to the BuildMaster and the Scheduler can be configured to build
after the tree is quiet for X minutes.

Documentation can be found here:
http://buildbot.sourceforge.net/manual-0.7.4.html#P4Source
http://buildbot.sourceforge.net/manual-0.7.4.html#Scheduler-Types
http://buildbot.sourceforge.net/API-0.7.4/buildbot.scheduler.Scheduler-class.html

Tony Walker wrote:
> Hi,
> 
> I have a buildmaster with several buildslaves. Our Perforce repository 
> resides on a separate machine on our network. What I would like to know 
> is how do I trigger a build on one of the slaves after a piece of code 
> has been checked in to perforce on a particular branch. Has anyone done 
> this before? We use triggers quite a lot in perforce, for example, we 
> have a script that emails changes to staff. So, how do I issue a command 
> to the buildmaster (that resides on a different machine) to start a 
> build after there has been a commit?
> 
> Thanks,
> 
> Tony.
> 




More information about the devel mailing list