Changelog

What’s New

CircleCI now supports Windows Server 2022. CircleCI has released a new Windows Server 2022 image which enables customers using CircleCI’s Windows executors to take advantage of the latest operating system, IDE (Visual Studio 2022), and software from Microsoft.

At this time, the Windows Server 2022 image will co-exist with the Windows Server 2019 image allowing you to have the option to upgrade while not losing support to your existing image.

For more information about this update, please refer to the Discuss post that has details on how to adopt the image.

What’s New in Release 2.19.14

Notes

In March 2022 updates to CircleCI server v2.x will stop. Support for customers using CircleCI server v2.x will continue.

• There has been a change to how you will checkout using tags in jobs. Branch tags will now be referenced by either CIRCLE_TAG or +refs/heads/tag/path. For example, git checkout --force "$CIRCLE_TAG" or git fetch --force origin '+refs/heads/master:refs/remotes/origin/master'

Fixes

• Security patches for the exim image
• Replaced deprecated GitHub API endpoint for teams

Known Issues

• On static (non-AWS) installations with NONE selected under storage driver settings, tests can be split only by file name or file size. If a user attempts to split tests by timing data, static instances will split them by file name instead.
• If any changes have been made to your networking configuration from the default, you should run the following steps to ensure you can use SSH to inspect your builds (for further information on SSH reruns see the SSH Rerun Guide):
  • For customers using AWS, make sure that you have the latest Launch Configuration configured for Nomad clients, and that exiting Nomad clients were spun up using the Launch Configuration.
  • On each Nomad Client machine, create /etc/circleci/public-ipv4
  • This file should contain the public (if applicable) or private IP of the nomad client

What’s New

On March 15, 2022, GitHub will be changing which keys are supported in SSH and removing unencrypted Git protocol. As a result of this change, any image you have used in a job from a project created between November 2, 2021 and January 13, 2022 will require a version of OpenSSH greater than or equal to version 7.2.

CircleCI has updated the version of OpenSSH for supported machine images and next-generation Docker convenience images in anticipation of this breaking change.

To avoid pipeline failures on Tuesday, March 15, 2022, CircleCI recommends that if you are using deprecated Machine images or deprecated Docker convenience images, upgrade to a supported image. If upgrading an image is not possible, you can regenerate SSH keys for impacted projects to avoid pipeline failures on March 15, 2022.

For more information regarding this change and how to regenerate SSH keys, please refer to this support article.

Before Upgrading

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

What’s New in Release 3.3.1

Fixes

• CircleCI runner can now be used when server is installed behind a proxy.
• Fixed a bug that was causing some intermittent broken dependency caches.
• Removed outdated cert trust stores from some images. They were found to be causing access issues to some server installations.
• Fixed a bug that was affecting runner updates.
• SSH reruns now work when server is installed behind a proxy.
• Replaced deprecated GitHub API endoint for teams.

Known Issues

• 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.

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

What’s New

A new update has been released for the standard 20.04 Linux images for both amd64 and arm64.

For more detailed information about this update, please see the Linux Machine Executor Images Discuss post.

What’s New

The new Clojure Convenience Image (‘cimg/clojure’) is now generally available. This image replaces the soon-to-be-deprecated legacy image (‘circleci/clojure’).

For more information on this release, please see the CircleCI Discuss post.

You may also find more information in the Clojure image GitHub repository.

What’s New

We have released a new image update for Windows, in addition to an update for Visual Studio 2019 16.11.9.0. You can access these updates via our “edge” tags.

For more information about this update and refresh, please see the Windows image update Discuss post

Before Upgrading

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

What’s New in Release 3.2.2

Notes

• The rerun workflow endpoint now returns workflow ID rather than the message accepted.

Fixes

• TLS is terminated outside of frontend so the SSL server has been completely removed from the frontend container.
• Moved the default certificate logic from KOTS to helm.
• Fixed the build agent image version used in server v3.x. The image used previously was causing problems with runner.

Known Issues

• 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.
• It is currently possible for multiple organizations under the same CircleCI server account to have contexts with identical names. This should be avoided as doing so could lead to errors and unexpected behavior.
• 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.
• Runner cannot be used when server is installed behind a proxy.
• Let’s Encrypt certificate generation does not work. You will need to provide your own certificates or use the default certificates provided.

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

What’s New

A new remote docker version (v20.10.11) has been released and is now available for use.

For more detailed information about the currently supported remote docker versions and how to run them, refer to the CircleCI docker technical documentation.

What’s New

CircleCI’s quarterly Linux machine images are now available. The following updated Ubuntu 20.04 images are available for both amd64 and arm64:

• ubuntu-2004:202111-01

This November refresh updates software included in the image, which can be found in this Discuss post.

Refer to the machine executor docs for more information about how to use the machine executor and these images.

What’s New

The new MySQL convenience image cimg/mysql is now in Beta. This image is designed to replace circleci/mysql which will soon be deprecated. We are actibely looking feedback from users during the Beta period.

For more information about this image, please refer to the Announcement thread on Discuss.

You may also find more information in the GitHub repo for this image.

What’s New

The new MariaDB convenience image cimg/mariadb is now in Beta. This image is designed to replace circleci/mariadb which will soon be deprecated. During this Beta perios, we are looking for feedback.

For nore information about this image, please refer to the following post in Discuss

You may also find more information in the GitHub repo.

What’s New

The new Redis convenience image cimg/redis is now in Beta. This image is designed to replace circleci/redis which will soon be deprecated. During this Beta periodwWe are looking for feedback from users.

For more information about this image, please refer to the Announcement thread on Discuss.

You may also find more information about this image in the redis GitHub repo.

What’s New

CircleCI will be deprecating all legacy convenience images on December 31, 2021 and moving to supporting only next-gen convenience images. This change is being made to better serve our customers, while ensuring that these next-gen convenience images are consistently reliable. The next-gen CircleCI convenience images are designed from the ground up for an execution environment, and designed to be faster, more efficient, and most importantly, more reliable.

For more information about this upcoming change, please refer to the following Discuss post, which can be found here

What’s New

The new PostgreSQL convenience image (cimg/postgres) is now generally available. This image replaces the soon-to-be deprecated legacy image (circleci/postgres).

• Refer to the following CircleCI Discuss post for more information about this update, which can be found here.
• You may also find more information about this release in the following CircleCI GitHub repository, which can be found here.

What’s New

The new Android convenience image (cimg/android) is now generally available. This image replaces the soon-to-be deprecated legacy image (circleci/android).

Refer to the following resources for more detailed information about this update.

• Developer Hub page
• CircleCI Discuss post
• GitHub repository

What’s New

The Xcode 13 RC image is now available on CircleCI macOS resource classes. This image replaces Xcode 13 Beta 5. For further details, please see the Image Manifest.

Note: This image contains potentially breaking changes for NodeJS and Ruby 2.5 users upgrading from Xcode 12 images. For more information about these potential changes, refer to the following Discuss post.

What’s New

Xcode 13 Beta 4 image is now available on our macOS resource classes. This image replaces Xcode 13 Beta 2.

For more detailed information about this release, please see the Image Manifest.

Note: This image contains potentially breaking changes for NodeJS and Ruby 2.5 users. Please see the Release Notes for more details.

What’s New

CircleCI’s quarterly Linux machine images are now available. The following updated Ubuntu 20.04 image is now available:

• ubuntu-2004:202107-01

This July refresh updates software included in the image. Refer to the machine executor docs for more information about how to use the machine executor and this image.

Please see the following Discuss post for more detailed information about these updates.

What’s New

In order to keep up to date with changes to Xcode, the following updates have been made:

Xcode 12.5.1 is now available

Xcode 12.5.1 is now available on CircleCI macOS resource classes. This image supersedes Xcode 12.5.0 which will be removed, and job requests will now be re-routed to Xcode 12.5.1.

Xcode 13 Beta 1 is now available

Xcode 13 Beta 1 image is now available on our macOS resource classes. This image enables developers to build and test their apps against iOS 15, tvOS 15 and watchOS 8 betas.

Xcode 13 Beta 2 is now available

Xcode 13 Beta 2 image is now available on our macOS resource classes. This image replaces Xcode 13 Beta 1.

For more information on these macOS updates, refer to the CircleCI macOS Containers page.

What’s New

Some users of our Windows executor images may have experienced a recent issue with nuget restore failing to download packages from the nuget.org package source when running choco install before running nuget restore.

To address this issue, the Windows executor image has been updated to include a user-wide NuGet config file with nuget.org configured as a package source.

For more information about this workaround, please refer to this Discuss post.

What’s New

A new Android machine image has been added, with support for nested virtualization and running x86 emulators. With this new image, you can now run Android emulator-based UI tests and other types of builds that require nested virtualization, on CircleCI.

For more information about this Android machine image, refer to the Discuss post that describes this new image.

You may also refer to the following Canny posts, which address specific customer requests and issues:

• Android x86 EmulatorSupport
• Nested Virtualization Support

What’s New

image: cimg/rust:1.43.0

This is a direct replacement for the legacy CircleCI Rust image (circleci/rust). You can find this image on Docker Hub, and the source code & documentation on GitHub.

What’s New

image: cimg/ruby:2.6.5

This is a direct replacement for the legacy CircleCI Ruby image (circleci/ruby). You can find this image on Docker Hub, and the source code & documentation on GitHub.

What’s New

image: cimg/openjdk:14.0

This is a direct replacement for the legacy CircleCI OpenJDK image (circleci/openjdk). You can find this image on Docker Hub, and the source code & documentation on GitHub.

What’s New

image: cimg/go:1.13

This is a direct replacement for the legacy CircleCI Go image (circleci/golang). You can find this image on Docker Hub, and the source code & documentation on GitHub.

What’s New

image: cimg/node:12.16

This is a direct replacement for the legacy CircleCI Node image (circleci/node). You can find this image on Docker Hub, and the source code & documentation on GitHub.