Changelog

What’s New

CircleCI’s CLI now includes an env subst command, which serves as a wrapper around the popular envsubst CLI tool. The command is used to substitute environment variables in a text string or file.

circleci env subst is available in both the local CLI and inside all CircleCI jobs (coming to CircleCI server v4.2+). More information and usage examples can be found in the docs as well as in this Discuss post.

What’s New

We now offer a way for you to immediately delete a DLC cache’s contents. You can do so via the CircleCI web UI, or the CLI. Refer to this support article for details.

When using Docker layer caching (DLC), a project’s cache can occasionally become corrupted, leading to failed jobs. Previously, the only solution was to stop using DLC, wait 3 days for the cache to become invalid, then turn DLC back on.

Before Upgrading

See the CircleCI server 4.1 release notes for upgrade notes for this release.

When upgrading from server v3.x you will need to install v4.0 before installing this version.

What’s New in Release 4.1.0

New features

• Air-gapped installation is now supported on server v4.1.
• Self-signed certificates or private certificate authorities are now supported when using GitHub Enterprise.
• For new installations, Tink can be used as the encryption backend instead of Vault.

Changes

• The minimum Telegraf version is now set to 1.8.14.
• Nomad and Vault images are now stored in templates, rather than hardcoded in charts.
• The Nomad Terraform configurations now have the Nomad port hardcoded. Previously this needed to be entered manually.

Database Migrations

The following databases will run migrations when upgrading this version.

• builds_service
• branch_service
• contexts_service_production
• orbs
• orb_analytics
• permissions
• webhook_service
• conductor_production

Fixes

• The Trigger Pipeline button in the web app now works for forked PRs, and an error message will be visible if the trigger fails.
• Fixed a bug that was preventing forked PRs from building if both the fork and original were building on CircleCI.
• Fixed a bug that was causing intermittent status updates for jobs in GitHub.

Known Issues

• Vault may not refresh its client token after a month of uptime.
• Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for public installations, but for private installs you would need to ensure that you can access the private IP advertised. For example, by using a VPN into your VPC.
• CircleCI 1.0 builds are not supported. If an attempt is made to run a 1.0 build, no feedback will be available in the application to indicate the cause of the issue. If a build is run on your installation and does not show up in the CircleCI application, users should be directed to use the CircleCI CLI to validate the project configuration and get details of the possible cause of the issue.

To learn more about Server 4.x installation, migration, or operations please see our documentation.

What’s New

The job status badges in the CircleCI UI now include a badge for “Infrastructure Failure”. This badge indicates that CircleCI has run into issues with the underlying infrastructure on which the job runs.

Previously, it was difficult for users to discern whether a job failed due to an infrastructure failure, or another cause such as a test failure. This change allows for more transparency about what happens with the execution of jobs.

Refer to the Discuss post for an example.

What’s New

We have added out-of-the-box shell support for Node and Ruby. Invoking Node and Ruby commands within CircleCI jobs can now be as simple as the following:

steps:
  - run:
    name: Check Node shell
    shell: node
    command: console.log("node")

Usage examples in other languages can be found in our documentation.

What’s New

We have rolled out the Arm Large resource class as a standard offering in our Free plan.

To access this resource class, use the arm.large value with the resource_class key in your configuration. More details can be found in our documentation.

What’s New

The orb source, orb info, and orb/config validate CLI commands have been updated to work successfully with private orbs.

While the orb source and orb info commands operate the same as they do for public orbs, the orb/config validate command is different.

For more information on how to use the updated orb/config validate tool, please refer to the Private Orbs technical documentation.

What’s New

In making recent updates to the IP ranges feature, a change was made which inadvertently added several new IPs and removed several existing IPs from the static list of IPs associated with CircleCI.

The static list of IPs on our docs page and the DNS records have been updated to reflect these new IPs.

Consumers of the DNS A record do not need to take any action. If you were relying on the static IP list, please update your records to the new list.

Before Upgrading

See the What’s new in server 3.x doc for upgrade notes for this release.

What’s New in Release 3.4.0

New Features

• Android images for the machine executor are now available. For more information, see the Using Android Images with the Machine Executor guide.
• The CircleCI Build Agent can now be pulled from a custom Docker registry if required. For more information contact customer support.
• You can now use Amazon Certificate Manager (ACM) to manage your TLS certificates. For more information see the installation docs.
• Kubernetes v1.16 - v1.23 are now supported.
• Workload Identities for installations on GCP are now supported. Workload Identities can be used as an alternative to static credentials. For more informations see the installation docs

Fixes

• Fixed a bug that was causing the jobs page and step output access to run very slow in the CircleCI web app.
• Fixed a bug that was causing the workflows conductor pod to crash and issues with StatsD metrics.

Known Issues

• Before installing v3.4.0 delete the deployment named circleci-server-kube-state-metrics.
• Prometheus is broken in KOTS versions 1.65.0 - 1.67.0. If you rely on this feature, do not upgrade your KOTS version until this issue has been resolved.
• Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for private installations, but for public installs you would need to ensure that you can access the private IP advertised. For example, by using a VPN into your VPC.
• CircleCI 1.0 builds are not supported. If an attempt is made to run a 1.0 build, no feedback will be available in the application to indicate the cause of the issue. If a build is run on your installation and does not show up in the CircleCI application, users should be directed to use the CircleCI CLI to validate the project configuration and get details of the possible cause of the issue.
• The KOTS admin console cannot be upgraded if your installation is set up to be behind a proxy. The proxy settings will be deleted and cause the KOTS admin console to break.
• Config files will now be stored in the chosen object store (e.g., AWS S3, Google Cloud Storage or Minio). Users can run into errors accessing certain pipelines, if these config files are deleted due to retention policies (e.g., AWS S3 Lifecycle).

To learn more about Server 3.x installation, migration, or operations please see our documentation.

What’s New

We’ve redesigned the project setup experience and made it easier for both new and existing users to set up new projects with CircleCI.

When you set up a new project, you can now quickly select an org and run through setup on a single page. We offer three different ways to set up your projects: use the .circleci/config.yml in your repository; commit a starter CI pipeline to a new branch; or go to a config.yml template that you can edit. We also indicate a time frame for each of the three methods (Fastest, Faster, and Fast, respectively), so you can choose the quickest project setup that also meets your needs.

What’s New

Network transfer information is now available for all jobs using a Docker executor (excluding remote Docker) on our Cloud platform. This feature can help you predict the cost of using the IP ranges feature as well as optimize IP ranges usage.

To view network transfer information, open the Resources tab within a given job’s details page in the CircleCI web app.

Read more about this update in our Discuss post.

What’s New

CircleCI has just release 7 new Insights API endpoints to improve pipeline observability and tracking. You can now access even more insights features such as:

• flaky tests
• workflow time series
• organization performance data
• project performance data.

For more information about these new endpoints, refer to the CircleCI API v2 Insights documentation.

What’s New

Your organization will now be able to take advantage of updated usage controls, which can reduce credits wasted on actions run by unregistered users. This is a function available on your CircleCI dashboard and can be enabled/disabled by your account admin.

This update helps your organization direct credit consumption away from invaluable actions. In app, an unregistered user will see a prompt to register themselves first before continuing to build. This makes it easier for the org to keep track of the user as well as spend, resulting in significant credits savings that could have otherwise been used towards running builds and pipelines.

For more information about usage controls, visit the Usage Control tab URL here: app.circleci.com/settings/plan/[githubORbitbucket]/[OrganizationName]/usage-controls.

What’s New

We have made some exciting updates to our free plan, including giving teams more build minutes and access to our most popular features formerly only available on paid plans.

Some features on our new Free plan include:

• Up to 6,000 build minutes per month. Choose the right resource class size (S-L) to optimize for speed and power, or to maximize your build minutes.
• Unlimited users. CI and CD work better with a team; bring everyone on board easily.
• The largest free resource classes on Docker, Linux, and Windows so you can choose the right compute for any job.
• Increased concurrency limits: now up to 30x on Linux, Arm, and Windows.
• Streamlined collaboration with private orbs: shareable CircleCI configuration packages.
• Security. Our top priority is protecting our users’ intellectual property and sensitive secrets such as keys, tokens, and credentials. Rest easy with a suite of security features and compliance certifications, including FedRAMP and SOC 2 Type II.

You can learn about the of the changes here:

• CircleCI Blog - https://circleci.com/blog/most-generous-free-cicd-plan/
• Technical Documentation - https://circleci.com/docs/credits/#free-plan

What’s New

When you use our Windows executors, you may now take advantage of a larger disk size of 200 GB. This increase in storage size unlocks scenarios where you may wish to download large amounts of software during job execution (ie. gaming engines).

For more information about this update, please see the Discuss for more details.

What’s New

SSH reruns have historically been run as independent jobs, rather than as part of a workflow. This makes those jobs difficult to track and manage, causing them to block customers with limited concurrency. We are now running SSH reruns as workflow reruns, so they will appear in the same way that “rerun from failed” workflows appear.

This will make reruns easier to manage and track since they will be connected to the pipelines and workflows they were in when originally run, both in the API and UI.

Note The CircleCI v2 API now supports enabling SSH for re-running workflows.

What’s New

You can now interact with private orbs via the CircleCI web app. A list of your organization’s orbs has been added on the Organization Settings page, and new private orb details pages that open in the orb registry have also been added as part of this release. The orbs list shows all public and private orbs authored by your organization / in your organization’s namespace(s), while the private orb details pages open in the Orbs registry and are flagged with a new “private” badge. Please note you will only be able to see these pages if you are logged in and authenticated; if you are not logged in, you will receive a 404 error.

With this update, you may select your preferred way to interact with orbs, which can be either the CircleCI CLI or the CircleCI App, while also being able to easily share private orb information with other users in your organization.

Note: This update will not add private orbs to the searchable Orb Registry, and un-published orbs will not have linked details pages.

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.

Early anecdotal evidence has shown that some customers that have used this page to upgrade their resource classes and noticed their jobs were completed quicker. Future updates will include enhancing the UX for highly parallelized jobs and adding a CTA for jobs for high CPU utilization.

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.

An example of what the timing tab looks like can be seen here.

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.

An example of what the timing tab looks like can be seen here.

The timing tab has been enabled for 25% of users in Optimizely. The plan is to roll out this new feature to a small segment of users to get early feedback.

Note This feature is currently in “preview” mode and is not available to all customers at this time.

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.

For security and control purposes, the Runner launch agent requires a specific configuration to enable these SSH connections. Full details are available in the Runner documentation.

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.

The first feature enhancement is a new orbs list that is available in Organization Settings. You can now see all orbs created by your organization along with key stats such as version, type, and usage.