Note from the publisher: You have managed to find some of our old content and it may be outdated and/or incorrect. Try searching in our docs or on the blog for current information.

CircleCI kicked off 2016 with a bang, we launched and expanded our product offering with CircleCI for OSX and CircleCI Enterprise. Our team has proudly shipped new products this past quarter, but we’ve also been hard at work releasing new features, upgrades and bug fixes that our uses have brought to our attention.

New and Expanded Features

This quarterly blog will take a moment to highlight the features we were proud to ship. If you can’t wait another three months for a feature recap, in real-time on our changelog. If you have feature requests or would like to report a bug, you can do that on Discuss. We love to hear from you!

Here’s What’s New

First class Phabricator support

Since the launch of our Tag build API, we are now able to support Phabricator first class. To read more on how to setup Phabricator with Circle you can read here. This feature request was partly driven by how popular Phabricator integration was on our Discuss forum.

Ability to select “Execution Environment”

Now you have the option to select which Ubuntu image you would like to use for building your project. We’ve added a new section called “Execution Environment” under “Project Settings”. There you select between Ubuntu 12.04 or Ubuntu 14.04 images. If you are building an OS X project, you can enable it under the “Build OS X project” section on “Execution Environment” settings page.

Per-Project Insights

You can now view per repo build status and build performance. Read more about it here.

API to retrieve latest build artifacts for a particular branch

We have added functionality to retrieve build artifacts for the latest completed, successful, or failed build on a given project branch. Read more about it here. It, too, was partly driven by how popular it was on our Discuss forum.

Tag builds API

We now support both annotated and lightweight tags. You can now supply ‘tag’ as a key in the JSON body for POST request. Read more here.

Build parameters now supported for tagged builds

Now you can use build_parameters even for tagged builds. This makes it consistent with other build triggering APIs. Read more here.

Support for both [ci skip] or [skip ci]

You can now use ‘[skip ci]’ and ‘[ci skip]’ since we have started supporting both. Read more here.

Python symlink behavior change

We have updated our handling of Python virtual environment. Previously, we created a symlink in your project root to the system ‘venv’ directory. We will no longer do this for projects created after March 11, 2016. If you need the new defaults to be overridden per-project or per-org, please email us at

Admin-only permissions

We have added logic to restrict any non-admin Github users from modifying project settings. You can enable this feature for your organization, or specific projects within your organization. GitHub members would still be able to use features like Re-build, Re-build via SSH & Re-build without cache. Reach out to if you want this enabled.

New environment variables

We have added 2 new environment variables, CIRCLE_REPOSITORY_URL and CIRCLE_BUILD_URL. These variables are available in your builds and give easy access to the URL of your repo on GitHub and the URL of the build on CircleCI. This very handy for adding metadata to automated deployments. You can read more about our environment variables in the Environment Variables section of our documentation.

Test summary now displays Junit format XML parse errors

We now display JUnit format XML output parse errors under the ‘Test Summary’ tab. If the build generates an invalid Junit format XML we will display a warning with filename and the line number where the error occurred.

Browser being unresponsive issue

We have fixed a number of issues contributing to build pages rendering browsers unresponsive. We are currently displaying the first 400,000 lines of console output and provide you with the ability to download your full log.

Maven dependency caching

Maven builds are now using dependency:go-offline instead of dependency:resolve during the dependency phase, so they should save all dependencies to the cache before running tests

We hope you’re enjoying all the new CircleCI features! If there’s a feature you’d like to see, add a request on Discuss, and if you’d like to join our beta program, the Inner Circle, you’ll get to try out our newest features before they’re made public. If you have any questions for us, we’d love to hear from you at