Update PEP 512 w/ status of CI and code coverage tests (#138)

This commit is contained in:
Brett Cannon 2016-11-22 15:05:47 -08:00 committed by GitHub
parent 409a43413e
commit 34196079db
1 changed files with 14 additions and 30 deletions

View File

@ -512,16 +512,18 @@ The name given to this bot in order to give it commands is an open
issue: `Naming the bots`_.
Continuous integration per pull request
'''''''''''''''''''''''''''''''''''''''
A CI service
------------
To help speed up pull request approvals, continuous integration
testing should be used. This helps mitigate the need for a core
developer to download a patch simply to run the test suite against
the patch.
There are various CI services that provide free support for open
source projects hosted on GitHub [#github]_. After experimenting
with a couple CI services, the decision was made to go with
Travis [#travis]_.
Which free CI service to use is an open issue:
`Choosing a CI service`_.
The current CI service for Python is Pypatcher [#pypatcher]_. A
request can be made in IRC to try a patch from
bugs.python.org [#b.p.o]_. The results can be viewed at
https://ci.centos.org/job/cPython-build-patch/ .
Test coverage report
@ -719,7 +721,6 @@ Optional features:
- `Handling Misc/NEWS`_
- `Handling Misc/ACKS`_
- `Pull request commit queue`_
- `Test coverage report`_
- `Bot to generate cherry-pick pull requests`_
- `Allow bugs.python.org to use GitHub as a login provider`_
- `Web hooks for re-generating web content`_
@ -733,12 +734,11 @@ Optional features:
(http://psf.upfronthosting.co.za/roundup/meta/issue592)
- Convert b.p.o patches to GitHub PRs
(http://psf.upfronthosting.co.za/roundup/meta/issue600)
- `Continuous integration per pull request`_
(https://github.com/brettcannon/cpython-ci-test)
- `Test coverage report`_
* Completed
- None
- `A CI Service`_
Open Issues
@ -794,23 +794,6 @@ The names must come from Monty Python, which is only fitting since
Python is named after the comedy troupe.
Choosing a CI service
---------------------
There are various CI services that provide free support for open
source projects hosted on GitHub [#github]_. Two such examples are
Travis [#travis]_ and Codeship [#codeship]_. Whatever solution is
chosen will need to not time out in the time it takes to execute
Python's test suite. It should optimally provide access to multiple C
compilers for more thorough testing. Network access is also
beneficial.
The current CI service for Python is Pypatcher [#pypatcher]_. A
request can be made in IRC to try a patch from
bugs.python.org [#b.p.o]_. The results can be viewed at
https://ci.centos.org/job/cPython-build-patch/ .
Choosing a test coverage service
--------------------------------
@ -822,7 +805,8 @@ best if a service could be found that would allow for thorough test
coverage, but it might not be feasible.
Free test coverage services include Coveralls [#coveralls]_ and
Codecov [#codecov]_.
Codecov [#codecov]_. Testing is occuring in the
https://github.com/brettcannon/cpython-ci-test repository.
Rejected Ideas