NAV

Frequently Asked Questions (FAQ)

What kind of applications can I build on CircleCI?

Linux: CircleCI is a very flexible platform so you should be able to build almost any kind of application that will run on Linux. It doesn’t have to be a web application!

Android: Although Android is not officially supported on 2.0 at this time, you can build Android apps on the 2.0 platform, this post has an excellent example of a customer successfully building Android on 2.0. Note that this example does not use the emulator so it’s not affected by the incompatibility between Docker and the Android emulator. We will explain ways to run the Android emulator in future 2.0 documentation updates. Full documentation for building Android apps on 2.0 is coming soon.

iOS: Building iOS apps is not yet supported on CircleCI 2.0. Please refer to our documentation for iOS on 1.0 until 2.0 support is available.

Can I build Windows applications?

We do not yet support building and testing Microsoft Windows applications.

Does CircleCI 2.0 run inference commands?

Currently, CircleCI 2.0 doesn’t infer anything from your project, but we have plans to replace our inference system before moving out of Beta. Until then, you’ll need to manually configure all jobs.

My project is running on CircleCI 2.0, but the build is frozen!

Builds often freeze due to syntax errors in config.yml.

Cancel the build, check your config.yml for proper indentation, and ensure that all jobs and steps have the required keys.

Can I use CircleCI 2.0 without creating base images?

Yes, you can use* one of ours!

The circleci/build-image:ubuntu-14.04-XL-922-9410082 image has the same content as the Ubuntu Trusty 14.04 image our web app uses. Just know that the image is fairly large (around 17.5 GB uncompressed), so it’s less ideal for local testing.

The image defaults to running actions as the ubuntu user and is designed to work with network services provided by Docker Compose.

Here’s a list of languages and tools included in the image.

*For now. The idea of a monolithic build image doesn’t fit well with the ethos of CircleCI 2.0, so we will eventually deprecate it.

How do Docker image names work? Where do they come from?

CircleCI 2.0 currently supports pulling (and pushing with Docker Engine) Docker images from Docker Hub. For official images, you can pull by simply specifying the name of the image and a tag:

golang:1.7.1
redis:3.0.7

For public images on Docker Hub, you can pull the image by prefixing the account/team username:

myUsername/couchdb:1.6.1

Can I use the latest tag when specifying image versions?

We highly recommend that you don’t. Read more about why we think you should Avoid Mutable Tags

I updated my Docker image, but my build is using a cached image. How can I invalidate the old image?

We don’t currently provide a way to invalidate cached Docker images. One way around this is to use image tags.

If you’re running a build on my-image:123 and you update the image, you can use a new tag to force a cache refresh. In this example, you could change the tag to my-image:456 and choose that image in config.yml.

Git isn’t installed on my primary image but the checkout still ran

If you see this message in the ‘Checkout Code’ stage of your build:

Warning: Git is not installed in the image. Falling back to CircleCI's native git client but this is still an experiment feature. We highly recommend using an image that has official Git installed.

It means that we’ve made use of go-git to do the checkout for you. Although this should be a reliable fall-back, currently there is one limitation: checking out with source caching is not supported yet. When go-git is used and source cache is detected, you will see the following error in the step.

Error: source cache is detected but currently not supported by CircleCI's native Git client.

When you see the error and if you want to keep using source caching, please use an image that has Git installed.

If you notice other unusual behaviors, please reach out to support or let us know on Discuss.