Lately, Travis CI builds have been sitting idle in a queued state for a very long time (30m+) before running. While we do not have a formal SLA for expectations around CI pipeline execution time, this is far beyond an acceptable response time. Further, travis-ci.org is being decommissioned.

Acceptance Criteria

• Select a CI pipeline service that can provide guarantees of prompt pipeline execution.
• Create and configure a CI pipeline for this repo that performs, at minimum, the same work as the current Travis CI pipeline.

Options

GitHub Checks

CircleCI

GitLab

Travis CI (Commercial)

...other?