[Buildbot-devel] Force scheduler accepting patch
h.sorby at auckland.ac.nz
Wed Oct 17 02:47:33 UTC 2012
Sure I'll give it a shot. I'm not too fimiliar with the codebase
especially anything twisted related. I would like to setup the testing
so I can do things like create fake svn commits are there any docs on
that, currently I use actual svn commits which fills up the logs with
lots of 'testing' commits. Up till now I have had only a user
experience with buildbot and made some minor mods to suit my needs.
I will start some work on this and see where it goes.
1. I am guessing that the try scheduler can accept a patch and that I
might be able to port this over to the force scheduler?
2. I'm not at all sure how I'm going to be secure on the contents of a
patch, or the result of it. One of my reasons for using the force
scheduler is that I can then only enable the patch functionality to be
applied through an authenticated user, whom presumably I trust.
3. A command line try client separated from buildbot and it's
dependencies sounds good, but I think not a necessity to get this working.
4. JSON input would be something I would also put in the 'would like to
5. Unit tests, yes just have to find out how to create them for buildbot
6. Docs, of course I love doing documentation (Just in case your mail
client doesn't show it that last bit was written using the 'sarcastic
On 10/17/2012 01:45 PM, Dustin J. Mitchell wrote:
> On Tue, Oct 16, 2012 at 8:22 PM, Hugh Sorby <h.sorby at auckland.ac.nz> wrote:
>> I have used the try scheduler to great success but what I would like to
>> do is be able to supply a patch file through the force scheduler. This
>> way a developer would not have to install buildbot to test out a new
>> feature. So my question is, is this possible? or maybe could this be
> It's not currently possible, but it's actually a great idea: replace
> the try scheduler with particular configurations of the force
> scheduler, and use HTTP POST to submit the requests straight to the
> force scheduler (or, probably better, to a closely related API
> endpoint). From what I can see, this would require:
> * Allowing force schedulers to accept a patch
> * Solving the relevant security questions - try allows anyone who can
> submit a job to execute arbitrary code on slaves, so we need to be a
> little careful
> * Writing a new try client that doesn't require Buildbot, or Twisted,
> probably. It'd be nice if this was a separate Python package,
> although it should probably be built out of the same repo as Buildbot.
> * Adding the ability to force based on JSON input, in addition to
> form-encoded data
> * Unit tests
> * Docs :)
> Compared to some of the other projects underway in Buildbot, that's
> actually pretty minor. Want to give it a shot?
More information about the devel