Migrate CI to GitHub Actions

[jacobtomlinson]

Due to changes in the Travis CI billing, the Dask org is migrating CI to GitHub Actions.

This repo contains a .travis.yml file which needs to be replaced with an equivalent .github/workflows/ci.yml file.

It also appears that this repo uses CircleCI and AppVeyor in addition to Travis. Perhaps we should consider consolidating under GitHub Actions.

See dask/community#107 for more details.

[GenevieveBuckley]

Thank you for the heads up!

[GenevieveBuckley]

I'd say this is the TODO list for this repository:

• Turn our conda .yml files into the equivalent text requirement files (can be pip installed into conda environments, or used directly in the CI)
• Create a github action for push/pull requests. Matrixed over python 3.6, 3.7, 3.8, and for Linux, Mac, & Windows.
• Add a testing step to the new release github action: Running test suite as part of PyPI release #147 #175
• Update the README build badge, as described by Migrate CI to GitHub Actions as Travis CI is ending their free OSS builds community#107 (comment)
• Update the documentation on how to create test environments locally to CONTRIBUTING.rst (sorry Kuya-san)
• Create a scheduled action to run tests(?) This repository often goes long-ish stretches without much activity and Gen is sick of finding out just before a conference that something broke the tests in the last couple of months. TST: Add testing to github action #173
• Consider simplifying release to PyPI with https://github.com/pypa/gh-action-pypi-publish

[GenevieveBuckley]

It's a pity the Travis announcement didn't come a few days before the SciPy Japan sprint...

[GenevieveBuckley]

This comment makes a good point: dask/community#107 (comment)

Each job has options such as OS selection and the option to specify a matrix.

A note of light caution -- currently if you have a matrix of say Python versions and OS in the same workflow file, if one of those matrix entries failed you can't restart it individually, you have to trigger a full re-run of everything defined in that file. On xonsh we've subsetted them into one os per workflow file so we can at least individually restart Windows runs or MacOS runs

[jacobtomlinson]

Thanks for adding a TODO and planning this out. I'm going to be working through other repos so happy to help out here too.

Create a scheduled action to run tests(?)

GitHub Actions makes this easy to add a new trigger which runs CI on master with a specified cron timing.

https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#schedule

However they disable cron actions if the repo hasn't been updated for 60 days. Not sure if that is what you mean by a long-ish stretch.

This comment makes a good point: dask/community#107 (comment)

Agreed it is frustrating to have to restart the whole lot, but it's more of their waste than ours. It's also an open feature request that hopefully they will get to.

[GenevieveBuckley]

I've been meaning to do this but never quite getting around to it.

However, the current Travis CI page is now also showing this warning (so we'll have to fix something soon): "Please be aware travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information."