On 6 November 2016 at 09:38, Brett Cannon <br...@python.org> wrote: > If you have experience with Travis and/or CircleCI, please look at the > issues and the configuration files to help test both services at their best > and submit PRs to that repo as appropriate. What I'm looking for is not just > the best build scenario coverage (i.e. as many compilers and OSs as > possible), but also fast solutions (e.g. don't bother building the docs on > every platform/compiler combo if possible). The goal is for PRs to have good > checks to make sure they don't break anything with those checks not taking > forever so that the turn-around time on PRs can be as fast as possible.
A couple of things worth noting on that front: directory filtering that looks at which files changed can make a decent difference. For example, if only Doc and Misc contain changes, then the entire compile-and-test aspect can be skipped, since it's just a docs change. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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