Migrating away from Travis-CI
- Dominant language
- C++
- Stars
- 17.6k
- Forks
- 4.1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 69
Description
On November 2nd, 2020, Travis-CI announced the end of unlimited support for open source projects.
Infra is therefore moving our CI offerings away from Travis-CI in order to keep our builds pipeline cost-effective
Deadline: December 31st 2022
Infrastructure is moving ASF projects away from using Travis-CI at the end of 2022.
Travis-CI to GitHub Actions: https://docs.github.com/en/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions
Contributor guide
Research direction
Start with the repository's Travis-CI configuration and read the linked GitHub Actions migration guide. Identify the build jobs that must move, then verify that the required builds run successfully on GitHub Actions and no longer depend on Travis-CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100