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.

See dask/community#107 for more details.

[jameslamb]

Could I take this? I've done a lot of GitHub Actions stuff, would be happy to help.

[TomAugspurger]

That’d be great, though I may be slow to review for the next week or two.

…

On Nov 7, 2020, at 12:52 AM, James Lamb ***@***.***> wrote: Could I take this? I've done a lot of GitHub Actions stuff, would be happy to help. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOISCQ5SQPAHJNDBKFADSOTVBJANCNFSM4THX5BAQ>.

[jameslamb]

ok thanks!

[jameslamb]

I started on this tonight and realized two things:

• dask-ml only uses Travis to build and publish docs, with doctr
• doctr is tightly coupled to Travis: https://github.com/drdoctr/doctr

It looks like there is some discussion about supporting other CI providers (drdoctr/doctr#351), but right now that's just a discussion.

So I think this is something that needs to be handled maintainers here, and that the choices are:

• do nothing with this repo and wait for doctr to add GitHub Actions Support (and/or help them do that)
• switch to readthedocs like other Dask projects:
  • dask/dask: https://readthedocs.org/projects/dask/builds/
  • dask/dask-cloudprovider: https://readthedocs.org/projects/dask-cloudprovider/builds/

[jrbourbeau]

Alternatively, some other repos in the Dask org are switching to using GitHub actions to build and deploy their docs. For example, here's what the relevant workflow for dask-tutorial looks like: https://github.com/dask/dask-tutorial/blob/master/.github/workflows/ci-build.yaml

[jameslamb]

Makes sense. Either way, just to be clear I think I should step away from this issue.

Setting up different integrations for pushing docs should be done by maintainers, since it will require things I don't have permission to do, like logging in to other services (like readthedocs) or changing repo settings (for GitHub pages).

[mmccarty]

Can this issue be closed with #754 or is there further work here?

[TomAugspurger]

Might be some further work if we wanted to move all of the jobs to GitHub actions. Right now it’s just the docs.

…

On Jan 30, 2021, at 6:51 AM, Mike McCarty ***@***.***> wrote: Can this issue be closed with #754 <#754> or is there further work here? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOIVFAOEBBRTQA6LY6UDS4P6FRANCNFSM4THX5BAQ>.

[mmccarty]

That's what I was wondering. I can take a stab at it, if GH actions are desired.

[jrbourbeau]

Closing as it looks like tests and code linting were moved over to GitHub actions in #863 (thanks @TomAugspurger). Feel free to let me know if I'm missing something and we can re-open as needed