Changelog

What’s New

The quarterly update across Linux images is now available. In addition to standard software updates, the following changes have been made:

• Heroku has been removed
• Java 11 has been removed and replaced by Java 17

For more details on this release, refer to the Discuss post.

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

Changes

• We have updated our PostgreSQL password requirements to allow special characters (except single or double quotes) in addition to alphanumeric characters.

Fixes

• For runner installations on server, you can now directly clone a repository with just the checkout step in .circleci/config.yml.

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.1 installation, migration, or operations please see our documentation.

Before upgrading

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

What’s new in release 4.0.4

Changes

• We have updated our PostgreSQL password requirements to allow special characters (except single or double quotes) in addition to alphanumeric characters.

Fixes

• For runner installations on server, you can now directly clone a repository with just the checkout step in .circleci/config.yml.

Known issues

• When migrating from 3.x to 4.x, workflow configuration migrations will run as an init job and the workflows-conductor-event-consumer and the workflows-conductor-grpc-handler pods will not start until the migration completes. Customers with large PostgreSQL databases should plan accordingly. Migration time can be reduced by scaling the workflow-conductor pods.
• 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.0 installation, migration, or operations please see our documentation.

What’s New

Updated Android images for both the Docker and machine executors are now available.

Note that the Docker image has been migrated to Ubuntu 22.04. The machine image remains on Ubuntu 20.04 and will be migrated to 22.04 in the next month. For more details, refer to the Discuss post.

What’s New

The Q1 update for Linux images is now available, using the following image tags:

• ubuntu-2004:2023.02.1
• ubuntu-2204:2023.02.1

This refresh includes standard software updates. Heroku will be deprecated leading into the Q2 updates for Linux images. For more details, refer to the Discuss post.

What’s New

A bug has been fixed in the circle-android utility in the machine image used in the Android orb, where the wait-for-boot step would hang.

The Android cimg and machine images will both be built using Ubuntu Jammy 22.04 in the near future.

Visit the Discuss post for more information.

What’s New

A new set of convenience images have been developed that focus specifically on deployment.

• cimg/deploy
• cimg/aws
• cimg/azure
• cimg/gcp

For more information, visit the Discuss post.

What’s New

Image updates for Windows Server 2022, including a variety of package updates as well as the lastest release of current.

For a full list of updated packages and examples using current, visit the Discuss post.

What’s New

The quarterly (Q4) revision updates package versions for the Linux family of images. The updated Ubuntu 20.04 and Ubuntu 22.04 images are both available on amd64 and arm64 architecture. Images can be accessed with the following tags:

ubuntu-2004:2022.10.1 ubuntu-2204:2022.10.1

More details can be found in the 2022 October (Q4) Update Discuss post.

What’s New

August updates are available for Android images. These updates include the removal of Android API levels 23 to 26. These API levels are no longer supported by Android and their removal helps eliminate bloat.

The latest updates can be accessed by using the image tag android:2022.08.1.

For more details, please refer to the August 2022 Update Discuss post.

What’s New

This release includes updates to the image current tag for Windows Server 2019, Windows Server 2019 - Cuda, and Windows Server 2022.

For more detailed information about this release, see the Windows image update Discuss Post.

What’s New

CircleCI has updated our Android images for June. This release updates key software versioning for the Android Docker image cimg/android, in addition to the Android machine image android:2022.06. The Android machine image has a new naming scheme.

For more information on this update, and the new naming scheme, please see the Android Images Discuss post.

You may also directly access the GitHub repository for this Android update by going to the cimg repository.

What’s New

The Q2 standard Linux images have been updated. A patch update was released for Heroku and Git fixes. The updated Ubuntu 20.04 and Ubuntu 22.04 images can be accessed with the following tags:

• ubuntu-2004:2022.04.2
• ubuntu-2204:2022.04.2

More details can be found in the 2022 April (Q2) Update Discuss post.

What’s New

The Windows Server 2019 edge images include OS updates and Windows Server 2022 edge image includes several updated packages (nvm, docker-engine) as well as OS updates.

For more information about this update, please see our most recent Windows image updates post on Discuss.

What’s New

A brand new convenience image focused on deployment, cimg/deploy, has been deployed in Beta. We are actively seeking feedback from users during this Beta period

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

You may also find this image in the CircleCI GitHub repo.

What’s New

CircleCI has updated our Android images for April. This release updates key software versioning for the Android Docker Image cimg/android, in addition to the Android Machine Image android:2022.04.1.

For more information on this update, please see the Android Images Discuss post.

You may also directly access the GitHub repository for this Android update by going to the cimg repository,

What’s New

The Windows Server 2022 edge image has been updated to include nvm.portable 1.1.9 and docker engine 20.10.14.

For more information about this update, please see the Windows Server 2022 Update Dicuss Post.

What’s New

This update includes CircleCI’s first ‘current’ release of Windows Server 2022, in addition to regular updates for Windows Server 2019 and Windows Server 2019 - Cuda.

For more detailed information about this update, please see the Windows image update Dicuss Post.

What’s New

The Android Docker and Android VM images have been updated for March, including the inclusion of Android Tiramisu.

For more information about this update, please refer to the CircleCI Developer Hub page.

You may also find more information in the CircleCI Discuss post.

What’s New

On February 15, 2022, the Ubuntu 14.04 and 16.04 Linux VM images used with our machine executor were deprecated, meaning there will be no new releases or support for these images moving forward. When these images reach end of life (EOL) on May 31, 2022, any pipelines that utilize Ubuntu 14.04 or 16.04 images will fail.

In order to prevent unexpected failures and enable you to begin moving to newer images, CircleCI’s Ubuntu 14.04 and 16.04 Linux virtual machine (VM) images will be temporarily unavailable in late March 2022 and late April 2022, and will become permanently unavailable as of May 31, 2022. During these temporary “brown-out” periods, if you are currently using either of these images, be sure to update your config with a newer Ubuntu machine image before the 14.04 and 16.04 images are removed at the end of May 2022.

For more information about how CircleCI will manage these updates, please see the Deprecating Ubuntu 14.04 and 16.04 blog post.

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.