#896: Replace try with a client for the force scheduler
------------------------------+--------------------
Reporter: marcusl | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.8.0 | Resolution:
Keywords: try, users, force |
------------------------------+--------------------
Description changed by dustin:
Old description:
> We have a "try" client defined which looks for a patch in a local
> repository on a developer's system, patches it up, and submits it to
> Buildbot. It's very ad-hoc, isn't very configurable, and hasn't gotten a
> lot of love.
>
> Now that we have a force scheduler, the better solution is for the try
> client to talk to a force scheduler, preferably using HTTP. The client
> should also capture and send e-mail address of the submitter so that
> notifications can be sent.
>
> This allows lots of flexibility on the master side: users can set up as
> many force schedulers as they like, with different builders, properties,
> permissions, and so on.
>
> == scope ==
>
> To make this project a summer's worth, it should aim to implement:
> * a new try client
> * improved support for DVCS's, where patches aren't required, but where
> the client must send a repository
> * protocol support in or for the force scheduler
> * per-scheduler authentication/authorization
> * migration information for users of the existing try functionality
New description:
We have a "try" client defined which looks for a patch in a local
repository on a developer's system, patches it up, and submits it to
Buildbot. It's very ad-hoc, isn't very configurable, and hasn't gotten a
lot of love.
Now that we have a force scheduler, the better solution is for the try
client to talk to a force scheduler, preferably using HTTP. The client
should also capture and send e-mail address of the submitter so that
notifications can be sent.
This allows lots of flexibility on the master side: users can set up as
many force schedulers as they like, with different builders, properties,
permissions, and so on.
== scope ==
To make this project a summer's worth, it should aim to implement:
* a new try client
* improved support for DVCS's, where patches aren't required, but where
the client must send a repository
* support in the master for sending force-build parameters to a force
scheduler via an HTTP rest call
* support for patches in the force scheduler
* per-scheduler authentication/authorization
* migration information for users of the existing try functionality
--
--
Ticket URL: <http://trac.buildbot.net/ticket/896#comment:16>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
