Changelog

• Addresses an issue with CloudWatch metrics not being reported correctly. UPDATE: some customers report this has not addressed their CloudWatch problems. The next release will have a new fix.

• Addresses an issue for installations pointing at github.com (rather than an instance of GitHub Enterprise) that prevented those installations from adding new projects.

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

• Fixes a bug that was causing lists of builds to be truncated in some circumstances.
• Fixes a bug where certain configurations of GitHub were not syncing email addresses properly.
• Fixes a bug where some users were seeing a beta UI that should have not have been showing up.
• Various minor UI fixes.

This feature enables sharing of global environment variables across projects. Refer to the instructions and examples in the Setting Contexts document and the Job Contexts Example section of Orchestrating Workflows.

This feature enables filtering on Git tags for jobs in workflows using CircleCI 2.0. CircleCI will not run a job for a Git tag unless a tags filter is specified. Refer to the instructions and examples in the Workflow Tags section of Writing Jobs With Steps and in the Git Tag Job Execution section of Orchestrating Workflows.

• Fixes a bug in new installs that prevented the first user from becoming an Admin.
• Fixes a bug with using the built-in Heroku deployment support.

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.

A fix to the pricing plan has been implemented which limits Linux plan capacity to the published maximum. As a result of this change, you may see builds queuing until the requisite containers are available.

This feature enables core dumps for projects using CircleCI 2.0. Get core dump files and push them as artifacts for inspection and debugging using the instructions in the Uploading Build Artifacts document.

For mobile, we have just released a build image that allows you to use the latest stable version of Xcode, 8.3.3. To start using it, add the following to your circle.yml:

  xcode:
    version: "8.3.3"

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:

The Workflows feature is available on CircleCI 2.0. It is designed with a flexible algorithm to support very complex job scheduling and orchestration using a simple set of new configuration keys. See the Steps to Configure Workflows section of the Migrating from 1.0 to 2.0 document for instructions. Refer to the Orchestrating Workflows document for examples and conceptual information.

• New Projects list in the Admin section gives you an overview of all projects across your entire installation of CircleCI Enterprise.
• New onboarding flow – new users will be prompted with a list of projects to follow drawn directly from their GitHub account.
• New option for users to choose “My builds” or “All builds” when viewing lists of builds.
• New JIRA integration for creating issues from a Build Page - configured under Project Settings.
• Option to externalize the underlying persistance storage (Postgres and Mongo) - talk to your CircleCI contact for details.
• Improved support for snapshot backup and restore via the Admin Console.
• Various performance improvements and minor bug fixes.

This feature enables users to log in to CircleCI with a Google account and provides new users with the opportunity to experience the application and selected demo projects without providing access to their code repository.

This update makes Xcode 9 Beta available for all macOS builds. Specify version 9.0 in your circle.yml file to override the default.

Now you can filter your build emails by project without doing subject matching. This feature adds the standard List-ID header with organisation.project.notifications.circleci.com to make it easy to filter build emails into per-repo or per-org folders.

This feature enables you to import project environment variables from projects in the same organization to save time and typing. On the Settings screen for your project, click the Import Variable(s) button on the Environment Variables page and select from the list.

This feature enables you to join CircleCI without providing access to your private GitHub repos. To limit access, select Public Repos Only from the Start with Github menu on the signup page.

This is a security update to prevent logging temporary access tokens in build output. Those access tokens would have allowed a user to do a PUT request to overwrite an existing artifact only if all of the following were true:

Looking for the builds most relevant to your actions? You can now filter builds by “my builds” (builds you triggered) or “all builds” (builds triggered by other users on your team). The filter can be found near the top, right-hand corner of your dashboard. Currently, this feature is only available on the organization and project-level.

A minor maintenance release, primarily to improve the single-box installation process for new trials of CircleCI Enterprise. Also, we have now follow advice from GitHub to not check if emails in GitHub Enterprise are “verified” — we will continue to check verified status if you are using github.com. If you have reason to change “verified” checks on your users’ emails let us know.

Note for Admins

This release requires extra steps than usual. Please see https://circleci.com/docs/enterprise/upgrade-for-1.46.x-and-earlier/ for detailed instructions.

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

The logs produced by the Fastlane tools are now being stored as build artifacts so that you can easily access them later.

It is now possible to control whether to run builds for pull requests coming from forks and whether to pass the secrets from the main project to the fork on such builds, via two separate settings. Check out the Advanced Settings tab for your project for more details.

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.

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.

It is now possible to upload provisioning profiles under the ‘Permissions’ section of your OS X project settings. Once uploaded, we will automatically import the profiles during your OS X builds. Profiles are encrypted at rest on the CircleCI side.

This update removes the need to keep the provisioning profiles checked into your repository and simplifies the setup of code signing for new OS X projects.

CircleCI offers the ability to link directly to build output steps. We’ve now extended this feature into build email notifications. You should now see a clickable ‘Failing Command’ on (failed) build notification emails which will open the build page to the failed command in your build output.

• Fix for a bug causing builders to not honor CIRCLE_CONTAINERS_SUBNET when passed in the initialization.
• Builds with high parallelism were experiencing slow performance on the build detail page in the web UI – this should now be improved.
• Some emails generated by CircleCI had hard-coded links to circleci.com. These should now point at your installation host.
• A handful of minor UI fixes.

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.

• Fix for a bug that stopped certain CloudWatch metrics from working.

• Fix for a bug that caused UI problems for certain Pull Requests

We have added a confirmation message to prevent users from accidentally stopping the builds on CircleCI.

• Minor changes to help debug some esoteric issues.

• Fixed layout problems in Safari on Mac.
• Fixed issue with tag builds interacting with the Auto-Cancel of Redundant Builds setting.
• Fixed performance of the build page, including awkward interaction when expanding build steps
• Fixed environment variables not sorting properly in project settings

We have added functionality to click through the ‘Build Timing’ graph to access different sections of the build.

• Note for Admins: we will now block your upgrade if there are pending migrations that need to be performed against your databases.
• We have changed the default behavior for builds with parallelism set above the current total container count in your build fleet. Previously we would auto-cancel any build with a parallelism above the total number of containers in your fleet. Those builds will now remain in the queue until the fleet is big enough to accommodate their parallelism setting. Builds behind those builds will continue to be bumped ahead, however, so the behavior is somewhat different than normal queuing behaviors, which is a strict FIFO model.
• New System Settings option to set the maximum parallelism for all projects. This allows you to prevent teams from using more of your fleet than intended.
• New option to auto-cancel “redundant” builds on a branch - found in the project settings, this new option allows you to set builds on branches other than your default branch to auto-cancel any builds on that same branch already running. This avoids running multiple simultaneous builds on the same working branch if you push several times in quick succession.
• On the Systems Settings page under Admin you can now enter “Container Tweaks” that will be run whenever containers are started in your build fleet. This feature allows you to make adjustments to the execution environment prior to builds running, so you can save time in each build. Note that these tweaks are only appropriate for things you want to apply to the environment for ALL of your builds.
• We now parse your circle.yml before the build runs and fail if there are errors. Before, the build would start and errors would be surfaced only once they caused a failure in a running build.
• Fixed a bug preventing artifacts from being generated in some circumstances after a failed build.
• The Artifacts API now allows cross-origin requests when requesting specific artifacts. In the past you could do this when using the API to get a list of your artifacts but not for downloading specific artifacts. You can now do both with the API.
• Fixed a bug that prevented some cases of triggering builds via the API. If you have had problems triggering builds with the API you may need to recycle your build fleet for this fix to take effect.
• Fixed a bug that would cause problems if someone’s access was removed from a project in GitHub Enterprise but that person’s token was being used by CircleCI Enterprise. Other users should now be able to continue using the project as expected if the original token’s owner no longer has access.
• Fixed a bug that prevented builds cancelled from the UI from actually cancelling in a timely fashion.
• Various design improvements such as better notifications and confirmation dialogs when changing various settings, new links on the build page and builds list to make it easier to link directly to specific containers or parts of your build output, better information for builds marked as “Not Run”, hiding some settings that aren’t applicable to Enterprise customers, and various minor improvements and bug fixes.

Users can show share link to a particular step within their build output; Eg. https://circleci.com/gh/spotify/helios/5091#tests/containers/0/actions/4

We have added flash notification when users add or remove Apple Code Signing key, API permissions, SSH key or environment variables.

• Fix for an issue that was causing builds to fail that were triggered by users with a github account but no circleci account.

Note: we are shifting our versioning to better reflect the current release semantically.

• PR-only builds - We have added functionality to only run builds when a pull request is open. To enable this functionality you can navigate to “Advanced Settings” for your project and enable the “Only build pull requests” option.
• Chrome notifications - see the docs
• Fixed a bug where builds triggered by people who don’t have seats in CircleCI Enterprise were not running. They now should run as before.
• Some UI changes to make updating data in the web interface more consistent.
• Reliability improvements by changing retry logic in various places.

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.

Bug fix: We’ve fixed a bug that --branch option was missing when --single-branch is used.

New Feature: Custom base URL for version control webhooks. When a new project is added, CircleCI will add a webhook to the GitHub repository of the project. With this new feature, you can override the default webhook base URL from the System Settings page under the Admin tools (available to designated administrative users). This feature is useful when your instance is behind firewall or other proxy and cannot directly receive webhooks from GitHub.

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

• Please Note: If you are using OS X builds you will need to run a manual migration as part of this release. After upgrading you will need to run this in a REPL: (circle.backend.model.esxi-vm/run-migrations!). Please talk with your account manager if you need further instructions.
• The Admin Users page now has links to the builds of each user.
• The API has a new endpoint /api/v1/admin/licensing that returns information about the number of seats available, number being used, when the license will expire, and how many inactive users there are in the system.
• Fixed a bug where links to the documentation broke.
• Various small bug fixes and UI improvements.

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