[core-workflow] Questions about the proposed workflows

[R. David Murray]

On Wed, 02 Dec 2015 18:58:34 +0000, Brett Cannon <brett at python.org> wrote:
> 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).

That's interesting.  I thought someone had already tried travis and our
test suite took too long to run.  Sounds like Kushal's stuff could be
hooked up to gitlab.

> > > 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

I don't think so.  For doing the commit-to-contrib association it seems to
me we should be looking at the VCS id, not the github id.  Since the VCS
id is supposed to be an email address, it can just go in the 'additional
email address' box in the tracker profile.  Or the primary.

> as automated as possible as I think Ewa still flips some bits manually.

Last I heard this was more policy than lack of infrastructure; I don't
know if that has changed.  But even if it is policy that Ewa (or her
delegate; I think someone else is doing the actual data entry now)
has to push the button, we could at least make it a single button.

--David