[core-workflow] CircleCI or Travis?

[Nick Coghlan]

On 19 November 2016 at 11:26, Brett Cannon <brett at python.org> wrote:
> https://github.com/brettcannon/cpython-ci-test has configurations for both
> CircleCI and Travis. If I'm missing something in either configuration then
> please let me know (e.g. there is still a free container to use on
> CircleCI). If I also missed a better CI service then also let me know (but I
> don't think I have).

My main question was whether we'd be able to eventually add the
manylinux1 build container to the pre-merge CI configuration, but it
looks like both services support that:

Travis: https://docs.travis-ci.com/user/docker/
CircleCI: https://circleci.com/docs/docker/

Of the two configuration files, I find the Travis one easier to read,
and the test matrix set up also makes it easier to see the results for
different configurations. It's also the preferred CI service for PyPA,
and I think consistency there will be helpful, especially if the PSF
ends up approaching our CI provider regarding either a paid account or
an in-kind sponsorship.

So call it +1 for Travis CI, -0 for Circle CI (I don't think the
latter would be a *bad* choice, I just think Travis is a better choice
for us specifically)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia