...
Please feel free to add columns if you see any other information that might impact the CI/CD needs of a project.
ProjectOS | Target Operating Systems | Languages, Build Tool | VCS Host | Developer Team Size | Concurrency | Build Tasks | Current solution / usage | ||
---|---|---|---|---|---|---|---|---|---|
OperatorFabric | Linux only | Java, Angular, Gradle | GitHub.com | 4 full-time developers, 2 occasional contributors (all in CET) We take advantage of the night to run a CRON job handling the publication of a SNAPSHOT version (docker and documentation) and a bot doing dependencies updates. | Currently we can only run one job at a time but more concurrency would allow us to run our API tests (Karate) and end-to-end (Cypress) tests in parallel. |
| We're currently using a paid 1-concurrent job plan on travis-ci.com. //TODO Alexandra Guironnet Add average minutes and number of builds once Travis insights are fixed https://app.travis-ci.com/github/opfab?tab=insights | ||
SOGNO | Self-hosted GitLab | Linux, (some services run on Windows and MacOS) | mainly C++ (cmake) and Python, (Rust, Java, JavaScript) | GitHub.com and mirrors to self-hosted GitLab | About 10 researchers plus a varying number of students (all in CET). | Integration of self-hosted GitLab CI with GitHub plus GitHub actions. GitLab runner can run multiple jobs in parallel. |
| We do not pay for any service but we are investing in our server infrastructure for GitLab. Migrated some jobs to GitHub actions but this is not possible for all jobs. | |
PowSyBl | Linux, MacOS | Free plan on GitHub Actions |
Solution/Platform Benchmark
...
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. |