This page details and compares available CI-as-a-Service (CISaaS) platforms for open source communities.
SCM Support by Platform
This table details the support for CI systems to report back the status of builds to SCM providers.
Gerrit | Github | GitLab | Bitbucket | Azure Code | |
---|---|---|---|---|---|
Jenkins | |||||
CircleCI | |||||
Azure Pipelines | |||||
Drone.io | |||||
Github Actions | |||||
GitLab-CI | † |
† https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/bitbucket_integration.html
Note: a similar approach could be used for other SCMs provided there is an API for updating CI status
Build Resources and Minutes
Builds, agents, runners: these are all different names providers use to refer to the compute machine CI/CD builds run on.
Builder Size | ARM Builders | External Builders | |
---|---|---|---|
Jenkins | N/A | N/A | Yes |
CircleCI | Yes/No | ||
Azure Pipelines | 2 vCPUs | Yes | |
Drone.io | Yes | ? | |
Github Actions | 2 vCPUs, 7 Gb RAM | Yes | |
GitLab-CI | 1 vCPU, 3.75 Gb RAM | Yes |