Move travis CI to github actions
Open
enhancement
- Dominant language
- Python
- Stars
- 49
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
The travis CI jobs we run now take over an hour to complete, they used to take 15 minutes.
**Describe the solution you'd like**
Move away from travis and use a CI provider that doesn't throttle our usage so heavily.
Contributor guide
Research direction
The issue names the current Travis CI jobs and GitHub Actions as the target, but specifies no files or tests. Start by locating the repository's Travis configuration and CI entry points, then compare job coverage and runtime. Done means equivalent CI runs on GitHub Actions without Travis throttling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100