[Buildbot-devel] tips for creating new P4-based source buildStep ?

Bill Deegan bill at baddogconsulting.com
Tue Mar 5 06:16:50 UTC 2013


On Mon, Mar 4, 2013 at 7:19 PM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:

> On Mon, Mar 4, 2013 at 7:45 PM, Stephan Koledin <skoledin at gmail.com>
> wrote:
> > Thanks in advance for any advice on this. I really just want to make
> > sure I'm headed in the right direction before committing to this
> approach.
> It sounds like you're on the right track - at least, your
> implementation will be nicely independent of any changes to the
> existing P4 support.
> That said, the P4 support hasn't seen much love recently:
>  * last modification was in May 2012, and that was removing
> functionality; before that, August 2011
>  * http://trac.buildbot.net/wiki/p4 lists the open bugs.
>  * MAINTAINERS.txt indicates Bill (copied) as the maintainer, but he's
> busy and we've been in short supply of P4 hackers
> If you're willing, it would make the world a better place to have a
> master-side P4 step that has the flexibility you need, plus full unit
> tests (so those of us who are not P4 gurus can maintain it).
> What do you think?

I have a functional master side P4 source step.
Lacking some tests at this point.
If you'd like to contribute to that branch rather than reinvent the wheel.

I was hoping to wrap this up at post pycon sprints coming up shortly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130304/dbb5e5d5/attachment.html>

More information about the devel mailing list