[core-workflow] Choosing a CI service

[Ryan Gonzalez]

FWIW, you said they're "CI services":

- CodeCov isn't actually a CI.
- AFAIK CodeShip doesn't work on Windows, so, for Windows CI, there isn't
really a choice *other* than AppVeyor.
- CodeShip seems to require an account just to view the build status.
- They're all failing. :(

On Fri, Aug 5, 2016 at 10:19 AM, Alexander Belopolsky <
alexander.belopolsky at gmail.com> wrote:

> I have recently set up several CI services in my cpython fork on
> Github: <https://github.com/abalkin/cpython/tree/ci>.
>
> I am not ready to make any recommendations, but feel free to click on
> the build badges at the top of the README file and see the results for
> yourself.  I activated the following services:
>
> * Travis CI
> * CodeCov
> * CodeShip
> * AppVeyor  (windows)
> _______________________________________________
> 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
>



-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160805/31f43089/attachment.html>