Changelog

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.

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

Fixes

• Patched some CVEs.
• Updated runner’s launch-agent to use a query string instead of a GET body.

Known Issues

• webhook-service is not operational when Vault is externalized.
• Vault may not refresh its client token after a month of uptime.
• Before upgrading to v3.4.x, 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 installations 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

Fail fast reduces wasted time and helps you optimize credit usage.

Configure your testing jobs to stop executing shortly after finding the first test failure, even in jobs where parallelism is enabled.

You can read more about the fail fast open preview in the Discuss post, and in the documentation.

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.

Before upgrading

See the CircleCI server 4.x release notes for upgrade notes for this release.

What’s new in release 4.0.2

Changes

• Pin Bitnami Postgres Helm chart url

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

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.

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

Fixes

• Fixed a bug that was causing delays and failures to update git commit statuses.

Known Issues

• webhook-service is not operational when Vault is externalized.
• Vault may not refresh its client token after a month of uptime.
• Before upgrading to v3.4.x 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 installations 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

The CircleCI VS Code extension is now generally available. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

By making existing CircleCI features available in VS Code and facilitating configuration file editing, the extension reduces context switching for CircleCI users (i.e. between the code editor and the browser).

Head to the VS Code Marketplace to view the full list of capabilities and download the extension for free.

What’s New

We have published the official CircleCI Visual Studio Code extension. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

By making existing CircleCI features available in VS Code and facilitating configuration file editing, the extension reduces context switching for CircleCI users (i.e. between the code editor and the browser).

Head to the VS Code Marketplace to view the full list of capabilities and download the extension for free. The CircleCI VS Code extension is currently in open preview.

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

Container runner, a more scalable and container-friendly self-hosted runner, has moved out of the open preview stage and is now in general availability.

Find more information about the release of container runner in the Discuss post. Read more about container runner in CircleCI’s documentation.

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

Project roles are a new feature that allows customers to limit organization-level access, while giving individuals or teams privileged access to specific projects. This feature is currently available for projects on GitLab SaaS support.

For more details on available roles and their permissions, refer to our GitLab SaaS integration documentation.

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

Changes

• Anonymous statistics reporting for Kong is now set to disabled by default.

Fixes

• Fixed a bug that was preventing email notifications from being sent with the following setting enabled: Notifications > Email Notifications> Build Notifications > My Branches.
• Fixed a bug that was causing a “Failed to load webhooks” error on project Webhooks pages in the CircleCI web app.

Known Issues

• webhook-service is not operational when Vault is externalized.
• Vault may not refresh its client token after a month of uptime.
• Before upgrading to v3.4.x 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.

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

Before upgrading

See the CircleCI server 4.x release notes for upgrade notes for this release.

What’s new in release 4.0.1

Changes

• When migrating to server v4.x, Telegraf configuration data is now decoded and available in your values.yaml file.
• Anonymous statistics reporting for Kong is now set to disabled by default.
• TLS settings are now available for Postgres.

Fixes

• Fixed a bug that was preventing email notifications from being sent with the following setting enabled: Notifications > Email Notifications> Build Notifications > My Branches.
• Fixed a bug that prevented webhook-service from working when Vault is externalized.

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

What’s New

Container agent is a new type of self-hosted runner in open preview. Container agent adds support for the Docker executor with self-hosted runners, as well as basic auto-scaling and integration with Kubernetes.

Read more in the Discuss post.

Refer to our documentation for more information.

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.

CircleCI server v4.0.0 is now generally available. The feature set for this release are equal to server v3.x. The installation and upgrade processes for v4.x have changed significantly.

Server v4.x offers greatly improved security handling, installation, and update processes. Server v4.x is installed using helm charts and images that can be pulled ahead of time to comply with your security processes. Installation processes can also use artifacts pulled from customer-managed registries. Server v4.x makes improved use of Kubernetes secrets and removes the requirement to grant permissions and network access to third-party tools.

Before upgrading

See the CircleCI server 4.x release notes for upgrade notes for this release.

What’s new in release 4.0.0

New features

• Two new Arm resource classes are now available xlarge and 2xlarge. For more information on using Arm, see the Arm docs.
• CircleCI server v4.x images and helm charts are available for licenced users.

Fixes

• Fixed a bug that was causing a huge quantity of error logs in the distributer-internal pod.
• Prometheus is no longer included by default in CircleCI server v4.x.
• The default concurrency limit has been increased to avoid it being reached.
• Docker layer caching volumes are now deleted after 3 days if unused. Previously they were deleted after 7 days.
• kong is now placed behind NGINX to simplify loadbalancer setup.
• The loadbalancer has been renamed from circleci-traefik to circleci-proxy.
• Workflow configurations that are stored in PostgreSQL will migrated to the Object Storage.

Known issues

• Telegraf needs to have its configuration overwritten and base64 encoded.
• 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.
• Webhook-service may not work with an externalized Vault.
• 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

GitLab is now generally available for CircleCI. You are able to connect to GitLab and run pipelines from your GitLab repos. GitLab support also offers a new model for roles and permissions in CircleCI, independent of the VCS. This gives you full control over users and their access permissions.

We will continue to release GitLab-related features in Q3. These include project roles, restricted contexts, scheduled pipelines, and auto-cancel redundant workflows.

Each user can create up to three free organizations. A free organization can have up to 10 projects. If you need additional organizations or projects, consider upgrading to a paid plan, or contact our Support team.

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

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.

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

Fixes

• Links and redirects within the CircleCI server web app now correctly send users to their server login page. Previously, these links were directing people to the CircleCI cloud login page.
• Improvements to the user experience when upgrading and migrating server versions.
• Root volumes created by VM service are now tagged with the custom tag set for instances in the KOTS admin console. This covers machine executor and remote Docker VMs.
• A bug was fixed that was presenting users who need to re-autorize with a 404.
• CircleCI cloud marketing items have been removed.

Known Issues

• Vault may not refresh its client token after a month of uptime.
• Before upgrading to v3.4.x 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.

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

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.