...
| travis-ci.com | GitHub Actions | GitLab (self-hosted) | |
|---|---|---|---|
| OperatorFabric | Platform stability has been good so far, and communication on maintenance or incidents is usually quick. Integration with GitHub was quite straightforward. The build configuration can sometimes be tricky, especially cache management, but the documentation is pretty good (at least on our use cases). We only add 2 interactions with the support team and the quality of the response varied greatly. | No experience with GitHub actions so far, we had looked into it in its early days and at the time we found that there was really too little documentation to try and reproduce our Travis build as GitHub actions. | |
| SOGNO | We have already migrated some GitLab CI jobs to GitHub actions. For the moment, it looks like we won't be able to migrate all jobs. Experience with GitHub actions is ok so far although the majority of our developers still prefers GitLab CI. | We are quite happy with the GitLab CI but since we are running a self-hosted instance, it is not easily accessible for external developers. GitLab.com is not as established for LF projects, which is why we are moving to GitHub,com and actions. |