Changelog

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.