Changelog

The CircleCI web app now shows how much time is saved on each job that uses the “rerun failed tests” feature.

Upon encountering a failed step, users now can solicit guidance at the press of a button. This takes away the need to copy and paste the error message into your favorite search engine to find out what the problem might be and how to fix it.

Admins can opt out of this experiment by navigating to the Advanced section of Organization Settings.

The feature is powered, currently, by OpenAI. The only data sent to OpenAI is the error message in the output from the failed step. Before the message is sent any sensitive information such as passwords or access keys is removed. None of the data provided is being used to train the model.

Let us know what you think in the Discuss thread.

GitHub authorization with CircleCI has changed for new organizations. When you authorize your CircleCI account with GitHub, you may find this will be done through our GitHub App, rather than the GitHub OAuth app. You can see which account type your organization has by heading to the CircleCI web app and inspecting the URL in your browser:

This style of URL indicates you authenticated with the GitHub App:
https://app.circleci.com/pipelines/circleci/UTxCZDiJ9MLGLC8hR1ZDmg

This style of URL indicates you authenticated with the GitHub OAuth app:
https://app.circleci.com/github/<your GitHub username>

For more information on this integration, please review the documentation

As of August 25, 2023 all projects now have an enhanced experience for viewing steps through the CircleCI UI. Benefits include:

• Vastly improved performance and rendering quality
• No cap on log output
• Terminal control codes are now processed in the UI
• URLs are clickable from the step output

More details are available in our Discuss post.

Before Upgrading

See the CircleCI server 4.2 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.2.1 & 4.1.5

Changes

• Introduced the ability to disable the org-level concurrency limit in distributor. For more information, see the docs.

Fixes

• Fixed a bug that caused the /v2/tasks and /v2/tasks/running endpoints on the runner API to return errors.
• Fixed a bug that caused the self-hosted runners page to appear in the side navigation, but this page is unsupported on server at this time.
• Fixed a bug that caused the Insights page to crash if a user tried to view job resource usage, which is is unsupported on server at this time.
• Fixed a bug where the NGINX Deployment replicas were hard-coded to 1 and did not respect the nginx.replicas value in the Helm values.yaml file.

Before Upgrading

See the CircleCI server 4.2 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.

From server v4.2, CircleCI server auto-generates some secrets if they are not present in the Kubernetes namespace. If you are upgrading from v4.1.x to 4.2, and you have managed Kubernetes secrets yourself, you will need to follow the steps outlined in the CircleCI server 4.2 upgrade guide to ensure the system knows some secrets already exist.

What’s New in Release 4.2.0

New Features

• Config policies now available as a preview on server. Use config policies to create organization-level policies to impose rules and scopes to govern which configuration elements are required, allowed, not allowed etc. See the Config policies overview for guidance on setting up config policies. To use config policies CLI commands with server v4.2, append all commands shown in the docs with --policy-base-url https://<CIRCLECI-SERVER-DOMAIN>.com
• You can now find your current server version by running: curl http(s)://<CIRCLECI-SERVER-DOMAIN>/version
• The 2xlarge+ resource class (32 vCPUs, 64 GB RAM) is now available for use with the Linux VM execution environment

Changes

• Introduced the ability to disable the org-level concurrency limit in distributor. For more information, see the docs
• By default, Server 4.2 auto-generates some secrets. If you wish to manage these secrets yourself, you should create these secrets (if not done already) and ensure Helm is aware so that auto-generation is skipped. See the CircleCI server 4.2 upgrade guide for steps.
• RabbitMQ version upgraded from 8.6.4 to 11.15.1.

New Services

The following new services are introduced in this release.

• policy-service

Database Migrations

The following databases will run migrations when upgrading to this version

• builds_service
• cron_service_production
• domain
• insights
• permissions
• conductor_production

Fixes

• Patched various security vulnerabilities.

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

What’s New

The “Rerun failed tests” feature is now generally available. Instead of executing all tests in the testing job from a failed workflow (including tests that passed), only failed tests are executed again. Rerun failed tests helps shorten time-to-feedback when a workflow has flaky tests.

Customers who have adopted the feature are seeing a savings of around 8 minutes per job, and 60% reduction in runtime. Learn more about rerun failed tests in our official documentation.

What’s New

The quarterly update for Linux images is now available. Note that Ubuntu 20.04 and 22.04 are both available on amd64 and arm64 architecture under the edge tag, and are scheduled to be promoted to the GA release next week.

More details on this release, including software updates, can be found in the Linux 2023 Q3 release Discuss post.

What’s New

Image updates are available for the June 2023 snapshot of Windows Server 2022, as well as the current tag. This includes Windows security and OS updates, and package updates for Windows Server 2022.

For a full list of updated packages and image usage examples, visit the Discuss thread for the June 2023 image.

What’s New

CircleCI Personal and Project API access tokens have a new format. Previously, token values included a 40-character hex string. Newly created tokens will now include a CCIPAT or CCIPRJ prefix for personal access tokens or project access tokens, respectively:

CCIPAT_<base58-UUID>_<40-char-hex string>

For example: CCIPAT_ULUhR6rJLxYbyzyrP19iMZ_8fb1e3510325f7f09361de22b9420346c53ca2cb

Existing tokens are not impacted.

What’s New

Starting this week, we are introducing updates to the UI for steps in CircleCI:

• Vastly improved performance and rendering quality
• No cap on log output
• Terminal control codes are now processed in the UI
• URLs are clickable from the step output

More details are available in our 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.4

Changes

• Introduced the ability to disable the org-level concurrency limit in distributor. For more information, see the docs

Fixes

• Fixed a bug that caused potential notification failures for pipelines and workflows. The bug affected communication between the legacy-notifier and builds-service services.

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.

What’s New

The “created at” date is now available for newly created project environment variables. This allows you to more easily identify which env vars have been recently updated, and change out those that are getting stale. This helps you implement best practices on secrets rotation within CircleCI.

Please note:

• The “created at” date is not available for existing project env vars. Existing env vars will display “older than {x} days” instead of a “created at” date.
• Env vars only support create and delete operations, so there is no “updated at” date associated with project env vars.

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

Fixes

• Query parameters are now supported on the task-agent download endpoint.

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 What’s new in server 3.x doc for upgrade notes for this release.

What’s New in Release 3.4.7

Fixes

• When using CircleCI runner, a repository can now be directly cloned with the checkout step in .circleci/config.yml.

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.