Changelog

What’s New

• CircleCI 2.1 config keys are now available for reusing commands, executors, and parameters to simplify your .circleci/config.yml file. See the Reusing Config document for examples and instructions. Refer to the Configuring CircleCI reference for 2.1 syntax requirements.

• We have released the Xcode 10 image on CircleCI 2.0. Add the following to your .circleci/config.yml file to select that version of Xcode in your jobs:

  macos:
  xcode: "10.0.0"
  

Note: A known issue, for which a fix is in-progress, prevents shipping iOS apps built on the Xcode 10 image to the App Store.

• For Cloud Container macOS plans, there is an improved flow for adding containers on the Plan Overview page. This can be found under Settings > Plan Overview.

What’s New

• New projects are now created with 2.0 config by default and have Build Processing enabled.

• CLI users are now prompted to switch to the updated CLI. All commands are backwards compatible, however some have been officially renamed. For example, the circleci build command is now an alias for the circleci local execute command.

• For Performance Plans, total build minutes and credit usage for top projects is now displayed on the Plan Usage page. This can be found under Settings > Plan Usage

• For Linux Plans, there is an improved path for adding containers on the Plan Overview page. This can be found under Settings > Plan Overview

• Disabled Fixed notification through email or chat, if you have defined workflows as part of your configuration.

What’s New

• A Rerun workflow from beginning button is now on the Jobs page.

• A 1.0 Project Badge for all projects still building on CircleCI 1.0 appears on Github.

• Builds for new projects now require a CircleCI 2.0 config. 1.0 builds are no longer available for new projects. Builds for new projects without a 2.0 config will be blocked.

• Updated error message when builds are not run if free minutes are depleted.

• Updated information architecture with redesigned Welcome page and navigation menu for CircleCI Documentation is now available.

What’s New

• Auto-cancel of redundant builds now supports workflows. Customers will need to turn on the Build Processing option under Advanced Settings in their project settings. See the istructions for Enabling Auto-Cancel for Workflows Triggered by pushed to GItHub or the API for details.

• A new version of the Local CLI is available. Customers using the existing Local CLI can update using the circleci-update command followed by the circleci switch command. Refer to Using the CircleCI Local CLI for the update instructions.

• Performance customers can now see the billing period dates on the Plan Overview page.

• A new Plan Overview page that shows the details for plan selection and a new Plan Usage page that shows usages for any applicable Linux and macOS plan.

What’s New

• The Workflows page of the CircleCI app now displays the username associated with rerunning a workflow, approving a job, or cancelling a job.

• Performance improvements were made for workflows pages that reduce the load time for all workflows pages.

• Custom Performance Plans now appear with active users for the month on the Plan Overview page.

• Alerts for users who have depleted the free Linux build minutes for the month.

What’s New

• The Xcode 9.4.1 image was released on CircleCI 2.0. To select version 9.4.1 for a job, add the following to your .circleci/config.yml file:

        macos:
          xcode: "9.4.1"

• If you are on the Performance Plan, you can now view available credits on the Plan Overview page of your Organization Settings in the CircleCI app.

Updates

• Fixed a known issue with the CircleCI workflows UI due to . period character in the workflows name.

• Fixed the interaction of the Workflows Rerun dropdown menu by restricting to open-source project users who are part of a GitHub organization.

What’s New

Preview of improved builds service

CircleCI has developed an improved builds service that is ready for preview. The improved build service is the first step to a healthy roadmap of parameterized commands, config reuse across projects, improved DRY support, and better error reporting.

A preview is currently available for a few of our most adventurous organizations this week, and we plan on rolling it out to more projects in the coming weeks before it is publicly available. If you are adventurous and want to switch to the new service, be sure to read the preview docs before requesting approval.

What’s New in Release 2.14

This release contains service migrations for contexts and is a required upgrade. The following updates and fixes are also of note:

Fixed: Pre-allocated VMs not being used. Customers reported that jobs using machine executor and setup_remote_docker were continuing to spin up (and terminate) new VMs at runtime instead of the pre-allocated pool.

Fixed: Unable to build in AWS region eu-west-2.

Updated: The title of the Builds page in the CircleCI application was changed to Jobs in several places to better reflect the structure of builds.

Updated: Contexts are now checked for unique naming across your installation of CircleCI instead of just within an organization. You will no longer be able to create duplicate context names within an account. Existing duplicates will be honored by the system, but should be changed to avoid future collisions. Please see the Contexts documentation for further information.

Updated: The test-results services cleans up the /tmp directory on restart and the JVM heap size increased from 256m to 512m.

Known Issue(s)

When a saved context is removed during the build graph phase it can cause a silent failure during job execution.
When using the none storage driver, the cache will not be saved. This means that you currently cannot use caching in CircleCI when you are using the none storage driver.

Migration Tools: The 1.0 migration center was updated with additional content and helpful tools to migrate projects from CircleCI 1.0 to 2.0.

What’s New

The following features and additions are now available.

• New Workflows Feature: If your project has a large number of tests, you can use the circleci tests split command to reduce your job run time. This feature is now supported with Workflows. For more information on how to set up test splitting, see the Splitting Test Files section of the Running Tests in Parallel documentation.

• EOL Tools: The 1.0 migration center has been updated with additional content and helpful tools.

• Performance Improvement: CircleCI has upgraded the mechanism that returns gettimeofday calls. As a result, heavy users of syscall will see an aggregate improvement in performance. Most noticeably this will improve the run time of projects with heavy usage of profiling tools and Xdebug with PHP.

• Added: This release adds a Plan Overview page for customers on the Performance pricing plan to enable Admins to see their selection from the Settings.

• Added: Customers who are still building on CircleCI 1.0 will now get a reminder to upgrade to CircleCI 2.0 in build emails.

What’s New in Release 2.13*

• Fixed: Due to a certificate not being imported jobs were unable to submit after a container restart.
• Fixed: Stability issues within contexts service.
• Fixed: vm-service issue where AWS ECS and EBS volumes were left used. Added better idempotent client retries, API eventual consistency handling.
• Added: vm-service EBS Volumes cache evictor. Docker Layer Caching EBS volumes get deleted after 14 days of unused. You can control the inactivity period in Installation Admin Settings page.
• Added: Periodic checks to scale down any unused long running instances (e.g. due to reduction in prescaling configurations, or or due to a bug preventing termination of VMs in timely manner).
• Added: Optimizations to speed up provisioning. Resiliency to network/external changes.
• CircleCI is excited to announce that users on AWS can now forward host (Services VM) and docker metrics via Telegraf , a plugin-driven server agent for collecting & reporting metrics, to AWS CloudWatch. This is is the first step into bringing you greater observability into your installation. To enable and configure please go tohttps://example.com/settings#metrics. In this release the following metrics may be enabled: Docker , Networking , Disk , Memory, and CPU. For more information please see the Monitoring documentation.
• CircleCI is enhancing visibility by capturing usage statistics of CircleCI installations. This aggregate data will be used to better support you and ensure a smooth transition off 1.0. This optional feature is automatically available when you upgrade to the latest version of your installation or once a support bundle is downloaded. Below are the metrics being captured. If you would like access to this data in order to better understand your users please contact a CircleCI account representative. Please reference exhibit C within your terms of contract and our standard license agreement for our complete security and privacy disclosures. For more information please see the Usage Statistics documentation.

Weekly Account Usage

Weekly Job Activity

* this release contains migrations and is a required upgrade

The installable version of CircleCI Server 2.9.0 includes the following improvements and bug fixes:

• Resolution for a potential LDAP injection vulnerability
• Addition of support for the following LDAP fields:
  • Group Membership
  • Group Object Classes

See the Authentication document for the steps.

• Addition of default values for OpenLDAP and Active Directory
• Stability and bug fixes for an issue with test results
• Improvements to ready agent logging for support bundles
• Stability fixes and speed improvements for provisioning remote Docker engine
• Reliability improvements for the permissions service client
• Differentiation between the LDAP login and email to remove email as the assumed login value
• Fix for a bug that deselected all projects when a new user logged in for the first time
• Fix for a bug that was preventing Workflows from working correctly when located behind a proxy
• Bug fixes and improvements for Contexts

The installable version of CircleCI 2.8.0 includes the following fixes and improvements:

• An issue involving pre-allocated remote docker, machine VM creation, and other VM usage on AWS when the on-host VM option is selected has been fixed.

• An issue with the VM provider timing out when waiting for SSH to connect has been fixed. This upgrade supersedes any custom values for the Number of SSH attempts for starting VM setting and adds an equivalent field named Timeout for waiting for SSH to connect to VM(s) that you must set.

The installable version of CircleCI 2.6.0 includes the following fixes and improvements:

• It is now possible to create multiple Contexts in the Organization Settings of the CircleCI app. See the Contexts documentation for details and naming conventions.

The installable version of CircleCI 2.5.0 includes the following fixes and improvements:

• This release fixes a problem with DNS resolution failure on alpine-based containers. This problem was observed in the 2.3 release and was fixed for some service containers in 2.4. The 2.5 update fixes the issue for all service containers.
• This release includes improvements to scaling and garbage collection in the VM Service that should improve performance for installations with heavy use of machine executors or remote Docker.

The installable version of CircleCI 2.4.0 includes the following improvements and changes:

• Audit logging - This feature makes available a downloadable log of system events from the CircleCI Admin dashboard. This is the first release of audit logging; more events and improved data in the logs will be delivered in subsequent releases. Find detailed information about the data fields for each event in the Audit Logging section of the Security Features document.

• LDAP integration - It is possible to enable a new CircleCI installation to authenticate users with OpenLDAP or Active Directory credentials. New installations may be configured to have users authenticate through LDAP, including Active Directory support. Refer to the Authentication document for instructions.

• New build-agent - The new build-agent fixes some cases in which users were unable to log into a running job with SSH.

• VM Service improvements - Autoscaling of the VM Service has been improved, so machine executors should have more consistent performance at scale.

The installable version of CircleCI 2.2.0 includes the following improvements and changes:

• New visualization for Workflows - When you click on a workflow in the CircleCI application, a diagram appears with the relationship of your jobs to one another and the complete sequence of the workflow.
• Updates to the onboarding flow - We now show a new user only projects already building on CircleCI rather than a list of all projects found in source control. This change was made to prevent inadvertent adding of projects to CircleCI during the onboarding process. We also added a confirmation dialog for any user opting to follow more than six projects and made it clearer how to add new projects not yet building on CircleCI.
• Support for object stores other than S3 - CircleCI 2.2.0 now supports the same object store options that are supported in 1.x. This is a prerequisite to future releases that will allow non-AWS installations of CircleCI 2.x.
• Updates to the VM Service; ACTION MAY BE REQUIRED IF YOU ARE USING AWS - The VM service has been updated to use volumes rather than persistent instances. This change allows operators to accommodate Docker Layer Caching with a smaller number of long-running VMs. If you installed using the suggested IAM permissions from prior versions you must update your IAM permissions with this upgrade. Refer to the policy template for the complete set of permissions.
• New Contexts feature; ACTION MAY BE REQUIRED IF YOU ARE USING THE HIGH AVAILABILITY CONFIGURATION - The Contexts feature uses a HashiCorp Vault secure storage mechanism. If your installation is running in HA mode, HashiCorp Vault needs to be externalized similar to the Mongo and Postgres databases. Refer to the Configuring High Availability documentation for instructions.

The release of CircleCI 2.0 for macOS enables your iOS projects to benefit from the significant performance, stability, and reliability improvements in the CircleCI 2.0 platform, including the following new features:

Workflows: Orchestrate jobs and steps with great flexibility using a simple set of new keys in your configuration. Increase the development speed through faster feedback, shorter reruns, and more efficient use of resources.

Advanced caching: Speed up builds by caching files from run to run using keys that are easy to control with granular caching options for cache save and restore points throughout your jobs. Cache any files from run to run using keys you can control.

Get started with the complete set of documentation for the macOS platform:

• iOS Project Tutorial
• Testing iOS Applications on macOS
• Setting Up Code Signing for iOS Projects

CircleCI 2.0 is a completely updated CI/CD platform that starts every run with a clean image which is automatically provisioned just-in-time for Linux jobs on the CircleCI application installed in your private cloud. The CircleCI 2.0 platform includes significant performance, stability, and reliability improvements along with first-class Docker support, Workflows (pipelines), Resource Allocation, and Contexts. The Management Console (Replicated) also includes new options for enabling 2.0 Builders and appropriate default settings.

If you have CircleCI installed you may access CircleCI 2.0 features on your current installation with no restrictions under your current agreement and support level. However, you must contact your CircleCI account representative for assistance with upgrading, to obtain migration scripts, and to receive a new license channel.

• CircleCI 2.0.0 is only available on AWS and may be installed with Terraform or manually.
• Teams may create a CircleCI 2.0 .circleci/config.yml file in their repositories to add new 2.0 projects incrementally while continuing to build 1.0 projects which use a circle.yml configuration file.

Documentation for the installable 2.0 application is available at CircleCI 2.0 Documentation for the following topics:

• Administrator’s Overview
• Administration FAQ
• Security Features
• Installing CircleCI 2.0 on Amazon Web Services with Terraform
• Configuring High Availability
• Administrative Variables, Monitoring, and Logging
• Introduction to Nomad Cluster Operation
• Backing up CircleCI Data

This feature adds the used minutes to your Org Settings > Plan Settings page. This feature displays used minutes against Linux machines. It expands on our current functionality which shows minutes used against OS X machines and is located on the same page: Org Settings > Plan Settings.

Data appears for Orgs with a billing date after Aug 31, 2017. So, a new org will immediately see minutes used, and existing orgs will see the minutes used appear within the coming 30 days, depending on the billing date for your plan.

Today we updated our Xcode 9.0 beta 3 image to Xcode 9.0 beta 5 (build version 9M202q) with the latest simulators.

You can use this image by specifying Xcode 9.0 in your circle.yml:

machine:
  xcode:
    version: "9.0"

This image tag will be automatically upgraded when new betas are released by Apple, until the final release of Xcode 9.

CircleCI 2.0 is a completely updated CI/CD platform that starts every run with a clean image which is automatically provisioned just-in-time for Linux and Android jobs on the hosted CircleCI application.

Configuration moves into the code in 2.0, so every developer can configure jobs directly in their working branch, teams can try new things without the risk of slowing anyone else down, and business leaders have the ability to operate large global teams with minimal overhead. CircleCI 2.0 prevents you from writing clean-up scripts because every run starts in the same state, eliminating the risk of polluting a test database or leaving files in places that cause problems for the next run.

The CircleCI 2.0 platform includes significant performance, stability, and reliability improvements along with the following new features:

• First-class Docker Support: Choose any image to run your job steps, customizable on a per-job basis on a particular Git branch. Speed up your run times with advanced layer caching. Build docker images with full docker CLI support and full support for docker compose. Support for all programming languages and custom environments that offer more predictable output. See Specifying Container Images for instructions.

• Workflows: Orchestrate jobs and steps with great flexibility using a simple set of new keys in your configuration. Share temporary files between jobs with workspaces for fan-in, fan-out, parallel, and sequential runs. Hold a workflow for a manual approval and restart a workflow from a failed job. See Orchestrating Workflows for details.

• Resource Allocation: Configure your CPU and RAM needs on a per-job basis at the branch level, see the resource_class documentation for instructions. Paid accounts may request this feature from their Customer Success Manager, non-paid users may request to get started by sending email to support@circleci.com.

• Insights: Access interactive charts and analyses in seconds. Visualize trends in your build history to identify and pinpoint bottlenecks. Understand all of your builds at a glance. View the builds that fail most, so you can fix the slowest tests to improve efficiency. See the Collecting Test Metadata documentation for information.

• Debugging with SSH and CLI: Perform local job runs, configuration validation and SSH in to builds for access to log files and debugging running processes. See Using the CLI documentation to learn about running local jobs and refer to Debugging Jobs over SSH for SSH instructions.

• Parallelism: Automatic provisioning of containers as they are freed without waiting for other jobs to finish. See the Parallel Job Execution documentation for examples.

• Advanced Caching: Speed up builds by caching files from run to run using keys that are easy to control with granular caching options for cache save and restore points throughout your jobs. Cache any files from run to run using keys you can control, see the Caching Dependencies documentation for strategies and steps.

• Demonstration Applications: See the Language Guides and Demo Repos to learn CircleCI configuration by example for applications written in Go, Javascript, PHP, Python (Django and Flask), Ruby on Rails, Java, Elixir, and Clojure.

• New Documentation: New and restructured documentation including an Overview, Hello World, Sample 2.0 config.yml File, simplified instructions for Migrating from 1.0 to 2.0, plus examples for Configuring Databases and Creating Custom Docker Images. Refer to the Migration FAQ for common questions and known limitations.