[core-workflow] Questions about the proposed workflows

[Brett Cannon]

On Wed, 2 Dec 2015 at 10:50 R. David Murray <rdmurray at bitdance.com> wrote:

> On Wed, 02 Dec 2015 18:34:49 +0000, Brett Cannon <brett at python.org> wrote:
> > And this bot doesn't have to do it, but we should definitely make sure we
> > have at least automated testing of all PRs on *some* OS and also a way to
>
> Kushal did some work in this direction (for unix builds), but we haven't
> done anything with it for a while.
>

Donald hooked up Travis to the GitHub test instance and runs the PRs using
both gcc and clang, so I know at least GitHub + Travis has us covered.
Barry has said that GitLab supports runners but you have to run them
yourselves. I would also be curious to know if we could get a test coverage
report somehow (e.g., can coveralls.io support be added and have it use
https://bitbucket.org/ned/coveragepy/src/787158b1da024fd57b9a4f05c35042b7cdbe74a1/coverage/fullcoverage/encodings.py
which
requires a checkout of coverage.py).


>
> > verify the PR contributor signed the CLA (the testing should be easy
> enough
> > on either and the CLA should be doable somehow).
>
> This should be easy enough to do via the xmlrpc interface to the tracker,
> or
> (better) the rest interface if/when it lands.
>

I guess it would simply require people to add their GitHub IDs to their
issue tracker profile. We probably should also make sure the process gets
as automated as possible as I think Ewa still flips some bits manually.

-Brett


>
> --David
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20151202/38ccca7b/attachment.html>