Migrate CI to GitHub Actions
See original GitHub issueDue 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.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Migrating to GitHub Actions
Migrating to GitHub Actions. Learn how to migrate your existing CI/CD workflows to GitHub Actions. Automating migration with GitHub Actions Importer.
Read more >Migrating from Travis CI to GitHub Actions
Introduction. This guide helps you migrate from Travis CI to GitHub Actions. It compares their concepts and syntax, describes the similarities, ...
Read more >Automating migration with GitHub Actions Importer
You can use GitHub Actions Importer to plan and automatically migrate your CI/CD pipelines to GitHub Actions from Azure DevOps, CircleCI, GitLab, Jenkins, ......
Read more >Migrating from CircleCI to GitHub Actions
Migrating workflows and jobs. CircleCI defines workflows in the config.yml file, which allows you to configure more than one workflow. GitHub requires one ......
Read more >Migrating from GitLab CI/CD to GitHub Actions
GitHub Actions and GitLab CI/CD share several configuration similarities, which makes migrating to GitHub Actions relatively straightforward.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing as it looks like tests and code linting were moved over to GitHub actions in https://github.com/dask/dask-ml/pull/863 (thanks @TomAugspurger). Feel free to let me know if I’m missing something and we can re-open as needed
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