This repo would be a good candidate to test using Azure Pipelines GitHub Actions. We have 24 jobs and AP gives 10 GHA gives 20 parallel builds. Travis CI only gives 5.
The main python-pillow/Pillow repo's AP GHA config can be used as a basis, it's running the Docker tests.
AP GHA now has cron too:
https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule
Once done, we can either remove or cut down the .travis.yml to a minimal, fast set (to finish quicker than AP GHA); as a backup and because it's an easy and more familiar thing for contributors to enable.
This repo would be a good candidate to test using
Azure PipelinesGitHub Actions. We have 24 jobs andAP gives 10GHA gives 20 parallel builds. Travis CI only gives 5.The main
python-pillow/Pillowrepo'sAPGHA config can be used as a basis, it's running the Docker tests.https://github.com/python-pillow/Pillow/blob/master/azure-pipelines.ymlhttps://github.com/python-pillow/Pillow/blob/master/.azure-pipelines/jobs/test-docker.ymlAPGHA now has cron too:https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yamlhttps://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule
Once done, we can either remove or cut down the
.travis.ymlto a minimal, fast set (to finish quicker thanAPGHA); as a backup and because it's an easy and more familiar thing for contributors to enable.