Everyone who expressed an opinion seems to explicitly prefer Travis over CircleCI, so that solves that debate. :)
I did end up disabling macOS builds as Travis has under-provisioned those machines to the point that it adds an extra hour to the CI run (goes from 1.5 hours to under 30 minutes by removing macOS). I left building against both gcc and clang as well as the doc build. Thanks everyone for the input! On Fri, 18 Nov 2016 at 17:25 Brett Cannon <br...@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). > > Otherwise please look at the output of both CI services and let it be > known which service you prefer (i.e. +1/+0/-0/-1 for both services). Ignore > the fact that the doc tests are failing as I have fixed that in Python 3.6 > and 3.7 already. Consider ease of reading the output, how long it took to > build (e.g. I might turn off macOS support on Travis because they seem to > have under-provisioned those machines), etc. >
_______________________________________________ core-workflow mailing list core-workflow@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
