[Buildbot-devel] Problem with perforce

Brian Warner warner-buildbot at lothar.com
Wed Jul 6 21:32:50 UTC 2005

> 		s(
> 		  step.P4Sync, 
> 		  p4port="", 
> 		  mode="copy"
> 		  ),

I'll also point out that the P4Sync step is *really* simple. It is just
barely smart enough to update (by running 'p4 sync') an *existing* workspace.
In particular, you must create and set up that workspace by hand before
letting the buildbot do anything with it. step.P4Sync is much less capable
than any of the other Source steps. It's named "P4Sync" instead of "P4"
because it doesn't do as much as a real P4 step would.

I'd happily accept a patch that implements a real step.P4 class: it should
probably take a client spec as an argument, with some kind of %s facility to
substitute in the absolute pathname of the slave's copydir, since that isn't
fully known to the buildmaster. I don't use Perforce myself, so I can't
really build this one on my own.


More information about the devel mailing list