Changelog

What’s New

Select users with pipelines enabled on their projects will see a banner on the Job Details page that enables opt-in to the experimental new UI as it is being built. This new UI includes the following:

• Improved organization of the Jobs page
• An option to open a specific step in a new tab
• Replacement for the current dashboard that lists recent Pipeline runs

Read more information in the Discuss post.

What’s New

When no additional user seats are left in your plan, new users will be blocked from initiating jobs.

The Plan Usage page has also been updated to include Unregistered user (previously Guest user) and Scheduled workflow in your user list if you are initiating jobs usging scheduled workflows.

What’s New

• The Documentation search bar has been completely redesigned and improved to provide a full page of aggregate results, see CircleCI Docs.

• The Org Switcher was updated to fix a display issue that caused users to be redirected to the wrong organization.

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

• 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

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

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.

Today we updated our Xcode 9.0 beta image to Xcode 9.0 beta 2 with the latest 10.2 simulators. To start using it, add the following to your circle.yml:

  xcode:
    version: "9.0"

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

A few weeks ago we started downloading CocoaPods specs from S3 instead of Git in projects that use our iOS inference. It is now also possible to download the specs from S3 in projects with manual configuration.

Please check out this Discuss post for an example of downloading specs from S3 via a circle.yml command.

We have released patches to our AMIs and other infrastructure to address CVE-2016-8655. We recommend all CircleCI Enterprise installations follow the instructions below to update both their Services box and their Builder fleet.

If you have any questions or difficulties please contact enterprise-support@circleci.com.

Update the Services box:

1. As always, ensure your data is backed up.
2. Shut down CircleCI in the Replicated console (or via the CLI).
3. Update the kernel using the provided install_kernel_master function below.
4. Restart the machine.

#!/bin/bash
function install_kernel_master() {
    echo '>>> Installing Kernel'
    apt-get update
    apt-get install linux-image-3.13.0-105-generic linux-headers-3.13.0-105-generic linux-image-extra-3.13.0-105-generic
    apt-cache policy linux-image-3.13.0-105-generic linux-headers-3.13.0-105-generic linux-image-extra-3.13.0-105-generic
}

Update the Builder fleet:

For the builder fleet, update the Launch Configuration to use the updated AMI from the list below:

• ap-northeast-1 = “ami-07f09d60”
• ap-northeast-2 = “ami-90588ffe”
• ap-southeast-1 = “ami-4f54f82c”
• ap-southeast-2 = “ami-040c3467”
• eu-central-1 = “ami-3465a35b”
• eu-west-1 = “ami-d70421a4”
• sa-east-1 = “ami-2e6bf242”
• us-east-1 = “ami-e68f89f1”
• us-west-1 = “ami-901c4af0”
• us-west-2 = “ami-0c57fc6c”

If you are using our Terraform scripts, you can download the new script https://github.com/circleci/enterprise-setup/blob/master/circleci.tf and run terraform apply. We’ve already updated the scripts to include the new AMIs, so terraform should launch new builders automatically with the patched version, and cycle your fleet.

If you are using a non-AWS environment, use the same method to patch your builders you used to patch the Services box.

If any of the above does not apply to your environment, or you encounter issues with your upgrades please contact: enterprise-support@circleci.com.

We have released patches to our AMIs and other infrastructure to address CVE-2016-5195. We recommend all CircleCI Enterprise installations follow the instructions below to update both their Services box and their Builder fleet.

If you have any questions or difficulties please contact enterprise-support@circleci.com.

Update the Services box:

1. As always, ensure your data is backed up.
2. Shut down CircleCI in the Replicated console (or via the CLI).
3. Update the kernel using the provided install_kernel_master function below.
4. Restart the machine.

#!/bin/bash
function install_kernel_master() {
    echo '>>> Installing Kernel'
    apt-get update
    apt-get install linux-image-3.13.0-100-generic linux-headers-3.13.0-100-generic linux-image-extra-3.13.0-100-generic
    apt-cache policy linux-image-3.13.0-100-generic linux-headers-3.13.0-100-generic linux-image-extra-3.13.0-100-generic
}

Update the Builder fleet:

For the builder fleet, update the Launch Configuration to use the updated AMI from the list below:

• ap-northeast-1 = “ami-59389e38”
• ap-northeast-2 = “ami-a2e236cc”
• ap-southeast-1 = “ami-a80fa9cb”
• ap-southeast-2 = “ami-53241930”
• eu-central-1 = “ami-5a59a035”
• eu-west-1 = “ami-e0c78993”
• sa-east-1 = “ami-3832af54”
• us-east-1 = “ami-d0396bc7”
• us-west-1 = “ami-76226916”
• us-west-2 = “ami-938420f3”

NOTE: The following AMIs are not maintained by CircleCI, but contain a patched version of stock ubuntu.

• gov-west-1 = “ami-34df6755”
• cn-north-1 = “ami-92f622ff”

If you are using our Terraform scripts, you can download the new script https://github.com/circleci/enterprise-setup/blob/master/circleci.tf and run terraform apply. We’ve already updated the scripts to include the new AMIs, so terraform should launch new builders automatically with the patched version, and cycle your fleet.

If you are using a non-AWS environment, use the same method to patch your builders you used to patch the Services box.

If any of the above does not apply to your environment, or you encounter issues with your upgrades please contact: enterprise-support@circleci.com.

New Feature: The maximum size of files that you can upload for caching during builds has been fixed to 5G. The size is now bumped 20G by default on CircleCI Enterprise and customers can also override the default value to even larger size.

To override the default value, you need to run the following in a REPL of Service Box.

(settings/set {:max-file-cache-bytes <max-size-by-bytes>})

To unset the overridden value and use default, run the following.

(settings/unset! [:max-file-cache-bytes])

This release fixes a bug in the URL structure used to serve build artifacts.

The artifact URL format was recently changed to handle security concerns related to CircleCI’s hosted offering. The security concerns do not affect CircleCI Enterprise customers, but the change caused issues fetching build artifacts in CircleCI Enterprise installations. This release reverts the CircleCI Enterprise artifact format and resolves the issue.

Please make sure that you are using the latest provision-builder.sh and init-builder-0.2.sh before you upgrade to this release:

https://s3.amazonaws.com/circleci-enterprise/provision-builder.sh

https://s3.amazonaws.com/circleci-enterprise/init-builder-0.2.sh

As part of this release we’re changing the behavior of artifacts to only serve an allowed set of content-types. This means we won’t serve .html files as text/html. This is a security risk on CircleCI Enterprise since artifacts are served on the same domain as the rest of the site – as a result, any user or malicious code used as part of your build can push a specially-crafted artifact and gain control of another user’s account.

If this is an issue, you can override this behavior by setting “Serve artifacts with unsafe content-types” in the admin console. We don’t recommend this, but we’re providing it for backwards compatibility.

This release also includes some changes to container networking. Containers now each use a /24 in the subnet 172.16.1.0/16 by default.

If this conflicts with your private network, or if you were editing lxc-net manually in order to fix a prior conflict, you can now use CIRCLE_CONTAINERS_SUBNET and CIRCLE_CONTAINERS_SUBNET_NETMASK_LENGTH on the builders to configure those.