Changelog

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.

What’s New

• It is possible to trigger workflows with the CircleCI API using a new endpoint. See the Trigger a Build by Project section of the CircleCI API Projects Documentation.
  • You must go to your Project Settings in the CircleCI app to Enable Build Processing (preview) as a prerequisite for using this endpoint.
  • IMPORTANT – This endpoint does not yet support the build_parameters options that the job-triggering endpoint supports.
  • You may safely go back by disabling the radio button for this feature on your Advanced Settings for your project if jobs or workflows fail the new build processing.

Resolved Issues

• Resolved a known performance issue which caused a frozen page for organizations with many branches.

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.

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.

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.

The button on the Jobs page has changed for jobs that run as part of a workflow. The rebuild options that are not compatible with Workflows have been removed from the button on the Jobs page. Jobs that ran as part of a workflow will only include the Rerun Job with SSH button on the Jobs page.

To rerun a job that ran as part of a workflow, you must navigate to the Workflows page of the CircleCI application and either rerun your entire Workflow or rerun your Workflow from failed jobs.

• Added support for 2.0 builders to use object storage other than S3 (mirroring the options from the 1.x releases).
• Support for private images in docker jobs, including support for ECR authentication.
• New VM service and build agent to address certain situations that resulted in build infrastructure failures.
• Better accommodations for using proxies throughout the core infrastructure.

This feature enables an interactive graph of your workflow configuration. Refer to the instructions and examples in the Orchestrating Workflows document.

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.

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.

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.

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.

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.

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.

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.

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