distributed tests of a patch

[Damien Lespiau]

On Thu, Jul 23, 2015 at 12:28:26PM +0000, Finucane, Stephen wrote:
> > Summary: it would be very nice to take into account some distributed tests
> > in patchwork.
> 
> Not only would this would help DPDK, but I also think this has broad
> appeal for many other projects (such as Open vSwitch or QEMU). The
> mailing list-based workflow is still a great option in the era of
> Gerrit/GitHub pull-request workflows, but accessible automated testing
> integration is basically nigh on impossible. Patchwork as it stands is
> a great complement to a development mailing list, but the addition of
> this pseudo-"CI integration" could be another killer feature.
> 
> I have been working on a similar feature on and off for a few months
> and will accelerate development of it now (est. end of next week). In
> the interim, I have included some links below where you can find my
> WIP code and documentation. I'd love to get peoples' feedback on these
> changes. Hopefully this is something people want, and (just as
> importantly for me heh) I'm going about it the correct way.
> 
> Cheers,
> Stephen
> 
> * WIP code
>   https://github.com/stephenfin/patchwork/tree/draft/status-api
> * "Stable" code (still rebasing though...)
>   https://github.com/stephenfin/patchwork/tree/feat/status-api
> * Feature "ticket"
>   https://waffle.io/stephenfin/patchwork/cards/55201a9f5748610f0090751d

FWIW, I'm starting to look at this again as well. I'd like to have
patchwork know about series first though, otherwise I don't think it
makes much sense to test patches in isolation. A rough plan:

  - Land the UI redesign I have around
  - Make patchwork learn about series (I probably have a "good enough"
    state of this work that needs rebasing ie. I group patch into series
    back from git send-email threads).
  - Expose "New series since the last time I checked" API, probably
    through the REST API that comes with the previous point
  - From there, I probably want to hook it to jenkins, either writing a
    new plugin or re-using one if the polling API is the same as another
    tool already does
  - Have some git integration where one can pull and apply a whole
    series to a tree (as the first step for testing the patches):
    $ git pw-am series 2341	# where 2341 is the series id of the
				# patchork instance configured in
				# .git/config

-- 
Damien