Change Details

Github now has its own CI/CD offering - [[ https://github.com/features/actions | Github Actions ]]. Rather than have yet another external entity (Travis) with root access to the project, we should move to Github Actions for our CI/CD needs.

Github now has its own CI/CD offering - [[ https://github.com/features/actions | Github Actions ]]. Rather than have yet another external entity (Travis) with root access to the project, we could move to Github Actions for our CI/CD needs. However, the Wikimedia Foundation soon plans to move repository hosting to Gitlab, so we don't want to spend the time setting up Github Actions if we're going to move away from Github in the near future anyway. The timeline for this move is currently unclear. In the meantime we should evaluate what our problems are with Travis, and determine whether we should just spend the time addressing those versus moving to another CI platform.

Github now has its own CI/CD offering - [[ https://github.com/features/actions | Github Actions ]]. Rather than have yet another external entity (Travis) with root access to the project, we shwe could move to Github Actions for our CI/CD needs. However, the Wikimedia Foundation soon plans to move repository hosting to Gitlab, so we don't want to spend the time setting up Github Actions if we're going to move away from Github in the near future anyway. The timeline for this move is currently unclear. In the meantime we should evaluate what our problems are with Travis, and determine whether we should just spend the time addressing those versus moving to another CI platform.