Changelog

What’s New

You can now review the CPU & memory utilization for docker jobs on CircleCI’s hosted cloud compute. A new Resources tab on the job details page displays this data and easy-to-consume graphs for docker jobs.

What’s New

The test parallelism timing experience feature is now generally available and enables you to view information on parallel test times and bottlenecks so you can take this information and act on it to run your tests faster.

What’s New

This update enables you to view information on parallel test times and bottlenecks so you can take this information and act on it to run your tests faster.

What’s New

SSH reruns are now supported for Runner jobs. Although you have been able to SSH into cloud jobs to debug and inspect the system during and after the run, you may now use these same techniques for your Runner jobs.

What’s New

If you use the CircleCI CLI, you may now use the CLI to run orb information for private orbs.

What’s New

Many customers have been asking for an easy way to manage the orbs they’ve authored, both public or private. To meet this need, we are rolling out a set of orbs usability enhancements inside the Circle app.

What’s New

Users can now sort by trends to access projects and workflows with the largest change/delta in a given time window. This feature will simplify discoverability and aid with quicker fixes/updates.

What’s New

We have updated the Plan Overview page, so organizations on our free plans can now learn more about the Performance Plan, see details on pricing / estimates and see our top features on CircleCI.

What’s New

Webhooks are now available to all users. A webhook enables you to connect a platform you manage (either an API you create yourself, or a third party service) to a stream of future events.

Several new features have been released to improve the user experience when setting up configurations.

There have been a number of feature and user experience updates made to the CircleCI platform, which are described below.

What’s New

CircleCI has now made job and workflow webhooks feature available in open preview for all customers. “Job completed” and “Workflow completed” webhooks send status data, which may include states like success, failed, or canceled whenever a job or workflow reaches a terminal state.

What’s New

On the Plan Usage page, you will now see their network transfer and storage usage data from saving and restoring objects such as workspaces, caches, etc.

What’s New

There is now a button on the top right of the Pipelines page, next to the “Edit Config” button, to manually run a new pipeline from the UI. You must first select a branch, and then the pipeline is run at the HEAD of that branch.

What’s New

In order to improve the overall user experience, the following updates and changes have been made to the CircleCI user interface:

What’s New

If you navigate away from an SSH job while it is running, there is currently no process for you to navigate back to the SSH job to cancel the job. If you are on a legacy container plan, this may cause a bottleneck in your queue, resulting in you having to contact CircleCI Support to resolve the issue.

What’s New

Previously available to all of our Scale plan customers, we are now allowing all paid customers to access up to 3 Private Orbs. Note that Scale Plan customers will still have full access to an unlimited number of private orbs.

What’s New

Some notable updates have been made to our sample configuration templates.

What’s New

A new logical statement has been added to the config called matches, which takes a map with two parameters: pattern and value. If the value is a regex match to pattern, the value will be returned as true. This type of regex matching in when statements enables customers who want to filter individual steps or entire workflows based upon branch or tag to do so in a more consistent way that matches whatever logic they want to use.

What’s New

Significant performance improvements have been made on the Plan Usage page to reduce page load times, ensuring high usage customers can access and load this page without page timeouts.

What’s New

Previously, the Insights experience was scoped at a single branch level. Starting from today, you can now access Insights data across all of your branches, making it easier to understand workflow and job performance across an entire project.

What’s New

The Insights landing page has been updated to provide users with detailed performance summaries for each project in an organization. With this update, we have also simplified the landing page to display performance per project and also made it easier for larger organizations to use.

What’s New

Previously, CircleCI orb version badges were generated through shields.io, with data provided by a small service that a CircleCI CPE member managed. Although this process was not officially managed by CircleCI, with this update, this feature now consolidates the entire orb version badge generation process within CircleCI.

What’s New

The Context REST API was built to enable secure secrets rotation and move towards having RESTful public APIs. In order to enable GA, our teams made the following improvements:

What’s New

The design on the usage summary on the Plan Usage page has been updated. The details shown are now based on the feature available on each plan type. This aligns the design across the different plan types to provide a more consistent user experience.

What’s New

Trends data is now available at the organization level. Additionally, trends for the Mean Time To Recovery (MTTR), Throughput, and Duration metrics have been added. As a reminder, Trends provides relative benchmarks for the 24-hour, 7-day, and 30-day time windows against previous time windows.

What’s New

You will now see a faster checkout step in your CircleCI jobs. The built-in checkout step now does a git clone without checkout, followed by checking out the branch (overwriting existing) at the SHA received from the VCS provider. In addition to speeding up the checkouts, a number of Git checkout-related issues have been resolved, resulting in improved reliability of the checkout step.

What’s New

If you have configurations set up to collect test metadata, you will now have an easier time understanding what tests may have failed. On each Job page with a failed test, there is now a box above the steps/tests/artifacts tabs with a summary of how many tests failed, how many tests ran, and links to the names of each test that failed. The links jump to the output of the test failure further down the page. There is also a copy button to the right of each name if you would like to copy the name and rerun it in your personal IDE.

What’s New

Insights now persists the current branch when navigating from the pipelines or workflow runs pages. The dashboard displays the current/selected branch instead of defaulting to main. Similarly, on the Insights dashboard, changing workflows on a given branch no longer results in the branch reverting to main.

What’s New

You can now access Trends data on the Job Insights page. As a reminder, Trends provides relative benchmarks for the 24-hour, 7-day, and 30-day time windows against previous time windows.

What’s New

You may now export the jobs table from the Insights dashboard as a CSV file. Downloaded reports can be used to run additional offline analysis or share with coworkers.

What’s New

Raw metric values are often difficult to interpret and perform actions on without context. The Trends feature provides additional context presenting a relative benchmark against previous performance, enabling you to retrieve more data and gain additional insight into your data. The workflow details page supports trends for the 24-hour, 7-day, and 30-day time windows.

What’s New

You will now be able to access a granular view of your network transfer and storage usage on the Plan Usage page. Storage consists of stored artifacts, workspaces and caches that are core to the CircleCI platform experience, while network captures data transfer such as retrieving a cache in a subsequent job or uploading the job’s artifacts. This change allows you to have more visibility, granularity and control over usage. For more information, including self-serve strategies for optimization, please refer to the Managing Network and Storage Use page for more information.

What’s New

You can now add any combination of SSH key cipher / encoding. Specifically, we now support the ed25519 cipher, openssh encoding, and keys are not restricted to using the older (now non-default) PEM encoding. For more information, see the SSH keys guide in our docs.

What’s New

We have improved the error experience on the Pipelines Dashaboard by surfacing the main error and collapsing the details. This allows for quick scan accessibility, reduces visual clutter, and makes for a more consumable format instead of the full stack trace.

What’s New

When a new organization has less than 20 pipeline runs within an project, a diagram is displayed to explain the concepts of job vs. workflow vs. pipeline.

What’s New

The “Pipelines” link in the CircleCI app sidebar, which leads to the cross-project Pipelines view, is now called the “Dashboard” for a clearer route back to viewing all your runs in one place.

What’s New

A selection of time filters have been added to the Insights workflow overview in the CircleCI app. You can now look at 24 hour, or 7/30/60/90 day time windows when reviewing your workflows Insights. Configurable time range is the most popular request on our ideas board, and we are excited to deliver a feature that gives you more granular control over your data.

What’s New

You can now easily filter the projects you wish to view on the Insights dashboard page in the UI. This makes navigation easier, allowing you to easily find and view the projects you care about.

What’s New

You can now follow and unfollow projects within your organization directly from the Pipelines dashboard. Previously all follow/unfollow options were only available through a redirect to the Add Projects page.

What’s New

Job links in the UI are now blue rather than black to make naviagation between pipeline elements easier.

What’s New

All organizations can now import environment variables from one project to another, as an alternative to using contexts to share them. This functionality was present on the old UI but initially not released on the new UI. All users can now access it by navigating to “Environment Variables” within project settings.

What’s New

Performance plan credit refills will now be triggered at 2% and refills will be no smaller than 25,000 credits (or 25%). For more information see our billing FAQs.

What’s New

Configuration validation is now available in the in-app config editor to visually show config status at the point of adding a config to your project.

What’s New

You can now toggle the auto-expand pipleines options on or off in the top-right corner of the pipelines dashboard. This is especially useful if you have pipelines containing many jobs, giving the advantage of keeping these pipelines collapsed, and if you have pipelines containing a small number of jobs you may prefer the auto-expand option.

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.