Changelog

What’s New

The new Custom Plan will automatically track your usage, be able to provide real-time credit usage and balance information, and produce reports to accounting for invoicing. You will also be able to use user seats and be billed via credits for the usage.

What’s New

Pipelines can now be triggered via the API for PRs (using PR number instead of branch), PR merge commits, and Forked PRs. This enables you to more easily validate new code from PRs. Triggering on PRs and PR merge commits offers the ability to better validate PRs in a programmatic way. Triggering pipelines on forked PRs is valuable for customers who have open source repositories that are frequently forked.

What’s New

All Pipelines are now listed with the commit SHA in front of the commit message, which links directly to the commit in your VCS. This gives you a quick way to get to commits in your VCS from the Pipelines page.

What’s New

Multiple contexts can now be used in a Workflow. Previously, workflows were limited to having a single context. Instead of passing in a string to the context key in the config file, a list may be passed containing the contexts to be used in the workflow. This makes updates to contexts easier to manage and more secure.

What’s New

Workflow Map connection lines are now straight and do not overlap. When you hover-over of a job, all dependencies from and to that job are highlighted.

What’s New

The ‘credits available’ section of the Plan Overview in the UI has been updated to clarify some confusion around understanding credit balance. The bar display has been removed and the credits balance is now clearly shown.

What’s New

The config error message shown when there is an empty config file on triggering a pipeline has been improved to both clearly state the problem, and provide a way to get back to project setup to add a config.

What’s New

Child orgs now get premium features, including resource class allowance and DLC, from the parent org when plans are shared.

What’s New

Commit messages are now displayed along with commit author on the Job page in the New UI.

What’s New

The button to manually add a config when starting a new project now reads “Use Existing Config”. Previously, this text read “Add Manually”. Through user research it was found that the new text directly encompasses many more use cases, including existing users with existing config ready to go.

What’s New

The Branch and Commit message columns have been combined on the pipelines dashboard view of the new UI making the page easier to scan for the information you require.

What’s New

The metadata section at the top of the Job page has been reworked to better group related concepts and include new labelling. This redesign makes it more clear which link is for which feature, especially for those not familiar with icons for branch, commit, PR etc.

What’s New

The Pipelines page has been redesigned to merge the Project and Pipeline number columns together and make the font smaller across the whole page. This change allows you to see more pipelines on the dashboard without scrolling.

What’s New

Non-admins can now see Plan Overview and Usage pages in the new UI.

What’s New

• Waiting indicates the time spent preparing a job to run due to Docker image choice and CircleCI infrastructure time.
• Queued indicates when you hit a concurrency plan limit, and your job isn’t running because other jobs in your organization are running first.

These two definitions were previously vice versa in the UI, which caused confusion due to discrepancies between usage in the UI and what most customers understood the terms to mean. We hope this change will avoid any confusion in future.

What’s New

You can now commit config directly from the Project Set-Up page to your repo with 1-click. The same config can also be downloaded and committed manually if preferred.

What’s New

Container cgroup limits are now visible when using the Docker executor. This means that container-aware build tooling will now correctly detect the number of CPUs and amount of RAM available to the job.

What’s New

The Plan Usage page in the new UI now includes a Compute tab, showing compute minutes and credits by executor type. You can also further filter the breakdown by projects. MacOS container plan users will also see overages within this tab.

If you are not currently on a usage plan, this page will show compute usage by credit and user to give an indication of what to expect on the usage plan.

What’s New

Previously, queue and wait times were hidden behind an information icon hoover-over. They are now in their own section in the Job Details header. User-research showed these items were hard to find and folks did not like them being hidden.

What’s New

Favicons for CircleCI job pages now reflect the status of the job. The icon becomes red for a failed job, green for success, and blue for still running.

What’s New

The new Plan overview page includes improved visualisations for credit usage, user seats and upgrade options. Access the Plan overview from the new UI sidebar.

What’s New

A link to the changelog is now on the Help menu, accessible from any core-app page.

What’s New

The new logic constructs allow for more powerful compilation-time decisions about which work to perform. Read more on our Discuss post.

What’s New

The default branch, usually master, is now pinned to the top of the branch selector list, as well as below in alphabetical order to prevent it being missed.

What’s New

You can now type to search for the project you need in the project selection dropdown on the Pipelines page.

What’s New

Roll out of the Share and Transfer Plan settings page has started in the new UI, making it easier for you to share, unshare and transfer plans.

What’s New

You can now type to search for the branch you need on the pipelines page.

What’s New

The new UI now includes a link to the status site. In case of incidents, this icon will update to yellow (degraded), orange (parial outage) or red (outage).

What’s New

There is now a “help” icon and button on the main navigation of the new UI. When expanded, this menu includes links to Docs, Discuss, Support, Premium Support, Orbs and Feature requests.

What’s New

You can now approve jobs with API v2. The new endpoint is POST /api/v2/workflow/:workflow-id/approve/:approval-request-id. The approval request id is the ID of a pending approval job, which will also be returned as an approval_request_id on approval jobs returned by the API. For more information see the API v2 docs.

What’s New

Colorized loading of step output has returned to the new UI on the Job Details page up to 6000 ANSI words.

What’s New

Slack has been a powerful way for orgs to get status updates and custom alerts. We’ve brought it back in the new UI under Project Settings to aid users to solve their problems more efficiently while remaining in their Slack workflow.

What’s New

When viewing the Pipelines page, the most recent pipeline and any failed pipelines will be auto expanded to show the jobs that ran. This gives a quicker route to accessing job step output.

What’s New

The Test Summary tab on the Job Details page in the New UI now displays green when tests pass, and red for failures. The number of tests run, or number of failed tests is also displayed.

What’s New

Previously, the number of parallel runs in use was displayed, now both this and the maximum available are shown. You can also hover over the adjacent information icon for further information.

What’s New

We have decreased the first meaningful paint time down to 1.96 seconds and improved load-time perception for the job detail page in the new UI.

What’s New

We are now making a RAM disk available for our Docker executor at /mnt/ramdisk. This has the potential to significantly speed up certain types of build. For usage, please check the docs.

What’s New

All non-HTML build artifacts on CircleCI now redirect to short-lived pre-signed cloud storage URLs. This change has been made to improve the performance of our artifacts hosting.

What’s New

You can now manually unblock an approval job from the Pipelines List page in the new UI. Originally this functionality was only available from the Workflows map. Read more about approval jobs here.

What’s New

If any of your scheduled workflows become unscheduled for any reason, you will now be notified by email.

What’s New

Autocommit is a new feature that allows you to commit a sample language-specific config direct to a new branch on your repo when adding a project, making it even quicker to start building on CircleCI. You can also edit the config prior to committing. These features are in addition to the option to manually commit a config file.

What’s New

When adding a new project to CircleCI, the project dashboard sidebar now dynamically displays language-specific docs and guides to help you get started quickly and get the most out of the service.

What’s New

CircleCI is making changes for a stricter permissions access. Going forward only GitHub administrators will be able to view and access the following pages in the CircleCI application:

What’s New

You can now show, create, delete and list Contexts via the CircleCI CLI. Run circleci update to get access to this new Context functionality.

What’s New

Project and branch names are now included in the navigational breadcrumb trail in the new UI, placing essential pipeline information in view and making it quicker and easier to navigate to the pages you need.

What’s New

The way build artifacts are hosted is changing to improve performance. Read our Discuss post for further details.

What’s New

From March 9, 2020, CircleCI will begin to enable pipelines for all projects. A pipeline contains all of the workflows (and the jobs inside those workflows) that CircleCI runs after a trigger on your project. A pipeline can be triggered by a pull request, a commit, or even an API call. Read more on our Discuss post.

What’s New

Get job run data, including status, credits, and duration, for each individual job within a workflow. More info here.

What’s New in Release 2.19.00

Requirements

• Before upgrading to Server v2.19 your Nomad launch configuration must be updated by following this guide. Server v2.19 uses Nomad version 0.9.3, so if you have externalized Nomad, contact your support engineer before upgrading.

New Features

• You can now customize resource classes for your installation to provide developers with CPU/RAM options for the Jobs they configure. For more information see our guide to customizing resource classes in Server v2.19.

What’s New

The following resource classes are now available to customers on the Performance plan: XL and 2XL for the Machine executor, and 2XL for the Windows executor.