Skip to content

Changelog

Keep up to date with our latest
releases and enhancements.

Release 3.2.1    

Before Upgrading

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

Release 3.2.0    

Before Upgrading

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

Release 3.1.0    

Before Upgrading

IMPORTANT: With this release, the frontend-external load balancer has been removed. The traefik load balancer now handles all incoming traffic. When updating from a previous server 3.x version, you will need to update the DNS record that was pointing to the frontend-external load balancer and have it point to the circleci-server-traefik load balancer instead. Remember, you can retrieve the external IP address or DNS name of your traefik load balancer by typing kubectl get svc/circleci-server-traefik in a terminal that has access to the cluster.

Release 3.0.2    

Release 3.0.2

  • Resolved a bug relating to artifacts disappearing after 30 days. The default settings for the artifact retention period have been updated to unlimited, and can be adjusted from the KOTS Admin Console.
  • Resolved a bug that made Traefik “unaware” of TLS certificate updates without requiring a manual restart of the Traefik pod. The Traefik pod will now restart automatically after any TLS certificate updates go into effect after the initial post KOTS deployment.
  • Resolved a bug in builds-service that was causing pods to crash as a result of running out of memory.

Known Issues

  • No support for external data stores (Postgres, Mongo, Vault). This feature will be implemented in a future release.
  • 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. This will be fixed in a future patch release.
  • 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.
  • CircleCI currently assigns a public load balancer for the frontend services. For some customers, their infrastructure or security groups won’t allow this. We will provide an optional internal local balancer for the frontend services in a future release.
  • Telegraf metrics collection customization is not yet available.

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

Release 3.0.1    

Release 3.0.1

  • build_agent version value updated, as the previous version was relying on a vulnerable version of PsExec.
  • Due to an issue that was causing duplicated checks in GitHub, environment variables for output-processor were reconfigured.
  • Adjusted deployment configuration for vm-service to handle out-of-order database migrations managed by Flyway.

Known Issues

  • No support for external data stores (Postgres, Mongo, Vault). This feature will be implemented in a future release.
  • 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. This will be fixed in a future patch release.
  • 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.
  • CircleCI currently assigns a public load balancer for the frontend services. For some customers, their infrastructure or security groups won’t allow this. We will provide an optional internal local balancer for the frontend services in a future release.
  • Telegraf metrics collection customization is not yet available.

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

Release 3.0.0    

What’s New in Release 3.0.0

Server 3.0 is now generally available. The newest version of server offers the ability to scale under heavy workloads, all within your own Kubernetes cluster and private network, while still enjoying the full CircleCI cloud experience. Server 3.0 includes the latest CircleCI features, such as orbs, scheduled workflows, matrix jobs, and more. For existing customers interested in migrating from 2.19 to 3.x, contact your customer success manager. Server 3.0 will receive monthly patch releases and quarterly feature releases.

Release 2.19.12    

What’s New in Release 2.19.12

Fixes

  • Removed support for 1.0 builder graceful shutdown on auto-scaling events
    • This alleviates Python 2 security vulnerabilities

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

Release 2.19.11    

What’s New in Release 2.19.11

Fixes

  • Fixed a bug that didn’t allow more than 50 aliases in a configuration

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

Release 2.19.10    

What’s New in Release 2.19.10

Fixes

  • Fixed a bug that caused ‘git checkout’ to fail in go-git.
  • Fixed a bug in the YAML parser in picard dispatcher to support config-str to have more than 50 YAML aliases.
  • Fixed a bug where s3 retention policy deleted test results from an older job.
  • Reduced the likelihood of ‘out-of-sequence’ commit statuses.
  • General security updates.

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

Release 2.19.09    

What’s New in Release 2.19.09

Fixes

  • Better handling of non-alphanumeric characters in authentication passwords for Docker executors. Fixed a bug that was preventing the use of ~ and ? in the Docker ID password field under the auth key.
  • General security updates.

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

Release 2.19.08    

What’s New in Release 2.19.08

Fixes

  • Fixed a bug that was causing parallelism to fail for static installations with NONE selected under storage driver settings.

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

Missing Ubuntu 14.04 AMIs in us-west-1    

It has come to our attention that an Ubuntu 14.04 AMI in us-west-1 has become inaccessible. If you are using this AMI you should move your Nomad clients to ami-0c7b2a20526d0c5ff. For information on supplying AMIs for your installation, see the VM Service guide.

If you are still running Ubuntu 14.04 please contact us to migrate to Ubuntu 16.04.

Release 2.19.07    

What’s New in Release 2.19.07

Fixes

  • Fixed a bug that was preventing authentication to China region ECR images in the docker executor.
  • Removed the recursive chown from startup of the fileserverd service. In instances of heavy usage this was causing the startup process to take a long time, or in some cases, startup was blocked.

Known Issues

  • 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

Release 2.19.06    

What’s New in Release 2.19.06

Fixes

  • Fixed a bug that was causing workflow statuses to be displayed on GitHub in the wrong order.
  • Introduced performance improvements to workflows-conductor that dramatically reduce CPU usage and latency.
  • Fixed a bug that was preventing use of an S3 storage region other than us-east-1 via an IAM user.
  • Fixed formatting type of SMTP passwords to ensure they are masked during setup.

Known Issues

  • 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 aplicable) or private IP of the nomad client

Release 2.19.05    

What’s New in Release 2.19.05

Fixes

  • Fixed a bug that could lead to the VM database ending up in an incorrect state in the event of a Services Machine crash or manual termination of VM Service instances.

Known Issues

  • 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 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 aplicable) or private IP of the nomad client

Release 2.19.04    

What’s New in Release 2.19.04

Fixes

  • Fixed a bug that was leading to support bundle creation timing out before the Services machine logs had been created, leaving only Replicated logs.

Release 2.19.03    

What’s New in Release 2.19.03

Before Upgrading

If you are using an IAM role scoped to a non-root path, you will need to unset the OUTPUT_PROCESSOR_USE_NAIVE_ROLE_MAPPING environment variable in your output processor customization script. See the Customizations Guide in our documentation for more information on using customization scripts.

Release 2.19.02    

What’s New in Release 2.19.02

Fixes

  • In the LDAP login flow we now use an anonymous form to POST LDAP auth state, rather than sending it as a GET parameter. Previously, when a user authenticated using LDAP, their username and password were sent in plaintext as part of a query parameter in a GET request. As requests are over HTTPS, this left usernames and passwords in request logs, etc. This issue is now fixed.

Release 2.19.01    

What’s New in Release 2.19.01

Fixes

  • Fixed a bug that was preventing some customers from upgrading due to a schema change in one of our library dependencies.

Release 2.19.00    

What’s New in Release 2.19.00

Requirements

  • Before upgrading to Server v2.19 your Nomad launch configuration must be updated by following this guide. Server v2.19 uses Nomad version 0.9.3, so if you have externalized Nomad, contact your support engineer before upgrading.

New Features

Release 2.18.03    

What’s New in Release 2.18.03

Features

Following our release of Windows support on the hosted offering of CircleCI, running VM-based jobs in Windows environments is now supported on CircleCI Server instances running in AWS.

Release 2.18.02    

What’s New in Release 2.18.02

Bug Fix

  • Fixed an error when setting CIRCLE_PUBLIC_FACING_SERVER_HTTP_THREADS or CIRCLE_ADMIN_SERVER_HTTP_THREADS above 50.

Release 2.18.01    

What’s New in Release 2.18.01

  • Introduced configuration for timeouts for the following HTTP calls to GitHub (GHE):
    • GITHUB_CONN_TIMEOUT
      • Individual configuration for connection timeout, default 5000ms
    • GITHUB_SOCKET_TIMEOUT
      • Individual configuration for socket timeout, default 5000ms
    • GITHUB_CONN_REQUEST_TIMEOUT
      • Individual configuration for receiving connection from connection pool, default 5000ms
    • GITHUB_TIMEOUT
      • Single configuration for all of the above timeouts
  • Improved performance and monitoring of output-proceessor

Bug fixes

  • Fixed an issue with Nomad garbage collection that had the potential to prevent jobs from being run for heavy workloads. This issue was fixed in v2.17.1 but regressed in v2.18.

Release 2.18.00    

What’s New in Release 2.18

Upgrading your installation

Our upgrade guide takes you step by step through the process of upgrading to the latest version of CircleCI Server, including any checks and updates required before starting the upgrade process.

Release 2.17.03    

What’s New in Release 2.17.3

New Features:

  • Added ability to place banners on login screens. See our guide here.

Release 2.17.02    

What’s New in Release 2.17.2

New Features:

  • Added and exposed the following metrics for operators:
    • picard.*
      • This will affect the execution services, the important ones are located in output-processor.
    • jvm.*
      • This will allow our operators to understand and monitor when certain services are running out of memory.

Release 2.17.01    

What’s New in Release 2.17.1

Bug fixes

  • Addressed a configuration issue with VM Service running into rate limiting errors when calling out to the AWS API. This prevented VM Service from spinning up machine and remote_executors.
  • Fixed issues around nomad garbage collection only garbage collecting every 4 hours. This could prevent nomad jobs from running in environments with heavy usage.

Release 2.17.00    

What’s New in Release 2.17

Known Issues

There have been reports of our backpressure settings being too aggressive due to lack of nomad garbage collecting, as well as issues with the Vm Service overwhelming AWS API Limits. If you are on 2.17, you should upgrade to 2.17.1.

Release 2.16.02    

What’s Fixed in Release 2.16.2

  • Bug Fix: Fix a rare condition that causes some threads to be stuck in certain use cases.

Release 2.16.01    

Fill out this form to receive updates about CircleCI through email.

Release 2.16.00    

Fill out this form to receive updates about CircleCI through email.

Release 2.15.00    

Fill out this form to receive updates about CircleCI through email.

Release 2.14.01    

This patch release fixes an issue introduced in 2.14.0. Please review the fix(es):

Fixed: Docker executor does not support configurable resource classes.

Release 2.14.00    

What’s New in Release 2.14

This release contains service migrations for contexts and is a required upgrade. The following updates and fixes are also of note:

Release 2.13.00    

What’s New in Release 2.13*

  • Fixed: Due to a certificate not being imported jobs were unable to submit after a container restart.
  • Fixed: Stability issues within contexts service.
  • Fixed: vm-service issue where AWS ECS and EBS volumes were left used. Added better idempotent client retries, API eventual consistency handling.

Release 2.12.1    

The installable version of CircleCI v2.12.1 fixes an issue introduced in 2.12.0. GitHub cloud integrations were unable to create new contexts.

Release 2.12.0    

The installable version of CircleCI v2.12.0 fixes an issue in which an error occurs when uploading artifacts to S3 by updating AWS SDK for Java from v1.10.69 to v1.11.328.

Release 2.11.0    

This release fixes an issue with overwriting the known_hosts.local file. The fix allows keys to remain and enables the CircleCI upgrade process to append keys.

Release 2.10.0    

The installable version of CircleCI v2.10.0 fixes an issue in which jobs were unable to submit after a container restart due to the certificate not being imported.

Release 2.9.0    

The installable version of CircleCI Server 2.9.0 includes the following improvements and bug fixes:

Release 2.8.0    

The installable version of CircleCI 2.8.0 includes the following fixes and improvements:

Release 2.7.0    

The installable version of CircleCI 2.7.0 includes the following fixes and improvements:

  • Improvements to remote Docker instance provisioning and cleanup on AWS.

Release 2.6.0    

The installable version of CircleCI 2.6.0 includes the following fixes and improvements:

Release 2.5.0    

The installable version of CircleCI 2.5.0 includes the following fixes and improvements:

Release 2.4.0    

The installable version of CircleCI 2.4.0 includes the following improvements and changes:

Release 2.2.0    

The installable version of CircleCI 2.2.0 includes the following improvements and changes:

Release 2.1.1    

  • Fix setting for certain proxy configurations.

Release 2.1.0    

  • Added support for 2.0 builders to use object storage other than S3 (mirroring the options from the 1.x releases).
  • Support for private images in docker jobs, including support for ECR authentication.
  • New VM service and build agent to address certain situations that resulted in build infrastructure failures.
  • Better accommodations for using proxies throughout the core infrastructure.

Release 2.0.3    

  • Added support for proxies to the VM Service/Remote Docker setup.
  • Fixed an issue in the mongo migration scripts when moving from 1.x to 2.x that caused some customers problems.
  • Move to using Docker 17.03.2 (downgrade) to solve occasional freezes when starting/restarting.

Release 2.0.2    

  • Fix an issue where users were unable to import large PostgreSQL data sets during an upgrade from 1.0 to 2.0