Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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. 


GerritGithubGitLabBitbucketAzure Code
Jenkins(tick)(tick)(tick)(tick)(tick)
CircleCI
(tick)
(tick)
Azure Pipelines
(tick)
(tick)(tick)

Drone.io


(tick)


Github Actions
(tick)


GitLab-CI
(tick)(tick)(tick)

† 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 SizeARM BuildersExternal Builders
JenkinsN/AN/AYes
CircleCI

Yes/No
Azure Pipelines2 vCPUs
Yes

Drone.io


Yes?
Github Actions2 vCPUs, 7 Gb RAM
Yes
GitLab-CI1 vCPU, 3.75 Gb RAM
Yes


SaaS

VMs

Docker

Attach External

Platform + Arch

vCPUs

Ram (Gb)

Disk (Gb)


CircleCI

*

Linux, OSX

2

4-8

100


Gitlab-CI

Linux

1

3.75

25


Azure Pipelines

Linux, OSX, Win

2

7

10


Bitbucket Pipelines

Linux

N/A

4-8

N/A


Drone.io (Cloud)

*

Linux: x86, ARM

N/A

N/A

N/A


Appveyor

Ubuntu, Win

2

6

N/A


  • No labels