Changelog

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.

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.