Changelog

Fill out this form to receive updates about CircleCI through email.

Note: It is currently a best practice to use a Services Machine with a minimum of 32GB of RAM. Starting in 2019 it will become required. See docs for our recommendation(s).

What’s New in Release 2.16

The following updates and fixes are also of note:

IMPORTANT We have upgraded Replicated to version 2.29.0 which requires Docker 17.12.1. Please follow the instructions provided in the Updating Server Replicated Version guide before upgrading.

New Feature We are excited to announce that you can now distribute your data and workload external to the Services Machine. The following services can be externalized; MongoDB, Redis, Nomad Server, RabbitMQ, Postgres and Vault. Please contact your CSM for the latest documentation.

New Feature Custom Metrics can now be accomplished via a Telegraf Output Configuration File. See the Custom Metrics section of the Monitoring section. Note: The Custom Metrics section in the admin UI been disabled in favor of a configuration file.

New Feature Users can now receive email notifications about Workflows

New Feature The PostgreSQL image has been updated to allow modifying the default configuration by creating the following file: /etc/circleconfig/postgres/extra.conf A list of configuration options can be found here.

Updated Removing EOL Banner on build emails

Updated VM Service stability improvements

Bug Fix Fix issue with contexts that would break after 32 days

Bug Fix Vault auth tokens will now renew periodically to prevent expiration

Bug Fix Fix for an issue where workflow listing pages would intermittently fail to render

Bug Fix We have fixed a small number of bugs affecting processing incoming web hooks from GitHub to CircleCI.

Bug Fix For installs that are using an HTTP or HTTPS proxy, the jobs will now ignore that proxy so that setup_remote_docker works.

Bug Fix Reduced the number of connections 1.0 builders make to the PostgreSQL database.

Security Fix Security fixes for potential cross-site scripting vulnerability and HTTP header injection vulnerability

Security Fix Forked PRs can no longer write the caches of parent projects by default for security reasons. It is possible to still write parent project caches from the fork if the “Pass secrets to builds from forked pull requests” (in Advanced settings) is enabled.

Update Improved metrics for VM provisioning for machine executor. This changed metric names, so if you are monitoring VM provisioning in your install already, you will need to reconfigure the monitoring dashboards for these new metrics.

• New metrics:
  • vm-service.gauges.available-vms and vm-service.gauges.running-vms replaced by vm-service.gauges.vms_by_status
  • vm-service.gauges.running-tasks replaced by vm-service.gauges.tasks_by_status
  • vm-service.gauges.oldest-unassigned-task replaced by vm-service.gauges.unassigned_tasks_age

Known Issue(s)

When a saved context is removed during the build graph phase it can cause a silent failure during job execution.
In some instances the metrics section becomes hidden in the settings page. Please see this Knowledge article for instructions.

What’s New

Orb elements can now be composed directly with elements of other orbs. For example, you can now have an orb that looks like the following:

orbs:

  some-orb: some-ns/some-orb@volatile

executors:

  my-executor: some-orb/their-executor

commands:

  my-command: some-orb/their-command

jobs:

  my-job: some-orb/their-job

  another-job:

    executor: my-executor

    steps:

      - my-command

          param1: "hello"

What’s New

• The CircleCI CLI command orb list now has an optional flag, --json, that provides machine-readable output. In addition, the CLI command orb source has been updated to allow you to pull any version, including dev versions, for example:

circleci orb source mynamespace/myorb@dev:foo
circleci orb source mynamespace/myorb@1.2.3
circleci orb source mynamespace/myorb@volatile

• Cloud Performance plans have been updated to display multiple periods of usage data on the Settings page.

• The CircleCI API documentation has been re-published with a completely new design and updated content, see the API Reference.

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

• 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

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.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