Skip to content

Frequently Asked Questions

Is Cirrus CI a delivery platform?

Cirrus CI is not positioned as a delivery platform but can be used as one for many general use cases by having Dependencies between tasks and using Conditional Task Execution:

  script: yarn run lint

  script: yarn run test

  only_if: $BRANCH == 'master'
    - test
    - lint
  script: yarn run publish

CI agent stopped responding!

It simply means that Cirrus CI haven't heard from the agent for quite some time. In 99.999% of the cases it happens because of two reasons:

  1. Your task was executing on Community Cluster. Community Cluster is backed by Google Cloud's Preemptible VMs for cost efficiency reasons and Google Cloud preempted back a VM your task was executing on. Cirrus CI is trying to minimize possibility of such cases by constantly rotating VMs before Google Cloud preempts them, but there is still chance of such inconvenience.

  2. Your CI task used too much memory which led to a crash of a VM or a container.

Mac OS X Support?

TLDR: not in the near future.

We are planning to spend Q2 of 2018 on supporting for AWS and Azure. We are going to revisit Mac OS support in Q3 2018. Cirrus CI has everything for running Mac OS builds except a computing service that can effectively schedule Mac OS VMs. Please let us know if there is such a service and we can try to work together to bring Mac OS support earlier 😉.

Only GitHub Support?

At the moment Cirrus CI only supports GitHub via a GitHub Application. We are planning to support BitBucket next.

Any discounts?

Cirrus CI itself doesn't provide any discounts except Community Cluster which is free for open source projects. But since Cirrus CI delegates execution of builds to different computing services, it means that discounts from your cloud provider will be applied to Cirrus CI builds.