Now that Travis CI is no longer a viable option for OSS projects ( SIMP-8790, ), we have to find alternative service(s) to handle our CI/CD automation. After discussing various possibilities, we're going to start by using GitHub Actions as the CI/CD coordination, and GitLab CI as the heavy lifting testing check.
Release/deployment activities will be handled through GitHub Actions
Testing (particularly acceptance tests) can be handled using GitLab CI and our GitLab CI Runners.
Depending on how the services perform, we will consider using GitHub Actions to handle matrixed spec/unit testing.