Start Building for Free

CircleCI Server v2.18 What's New

6 months ago2 min read
On This Page

WARNING: CircleCI Server version 2.x is no longer a supported release. Please consult your account team for help in upgrading to a supported release.

This document provides a summary of features and product notes for the release of CircleCI server v2.18. For a full list of changes, including patch releases, refer to the changelog. For a step by step guide to upgrading your CircleCI Server installation from v2.17.x to v2.18, see our upgrade guide.

Requirements for upgrading

Notes and best practices

  • We now require a minimum 32GB of RAM for the Services Machine.
  • We have made some changes to our Redis configuration. If you have externalized Redis then you’ll need to update your configuration. Please contact your Customer Success Manager.
  • We have also made changes to our Postgres version and require at least postgreSQL v9.5.16. If you have externalized postgreSQL then please update to at least that version in 2.17.x before upgrading to 2.18.

What’s new in release 2.18.3

What’s new in release 2.18

  • It is now possible to restrict environment variables at run time by adding security groups to contexts. Security groups are defined as GitHub teams or LDAP groups. After a security group is added to a context, only CircleCI users who are members of that security group may access or use the environment variables of the context. For more information see our guide to restricting a context.
  • Customers running storage drivers external to AWS will see improved routing times when searching for build Artifacts.
  • You can now customize the metrics that get output from CircleCI. For steps and options, see our Custom Metrics guide. Below is a short list of metrics that are included by default when enabling Custom Metrics:

circle.backend.action.upload-artifact-errorTracks how many times an artifact has failed to upload how many builds flowing through the system are considered runnable
circle.dispatcher.find-containers-failedTrack how many 1.0 builds
circle.github.api_callTracks how many api calls CircleCI is making to GitHub
circle.http.requestTracks the response codes to CircleCI requests
circle.nomad.client_agent.*Tracks nomad client metrics
circle.nomad.server_agent.*Tracks how many nomad servers there are how long it takes for a runnable build to be accepted
circle.state.container-builder-ratioKeeps track of how many containers exist per builder ( 1.0 only )
circle.state.lxc-availableTracks how many containers are available ( 1.0 only )
circle.state.lxc-reservedTracks how many containers are reserved/in use ( 1.0 only )
circleci.cron-service.messaging.handle-messageProvides timing and counts for RabbitMQ messages processed by the cron-service
circleci.grpc-responseTracks latency over the system grpc system calls

  • You can now provide individual AMIs for both Remote Docker and machine executor jobs. Previously we provided the option for a single custom AMI to be used across both, but with v2.18, this expanded customization gives you greater control over versioning and dependencies to meet your individual CICD needs. See the VM Service guide for more information.

Fixed in release 2.18

  • Additional fixes around contexts and org renames.
  • Fixed an issue where occasionally volumes would fail to attach to spun up Remote Docker/machine instances.
  • Fixed an issue where the CircleCI integration could not be installed on JIRA instances with the subdomain.
  • Fixed an issue where the Workflows page would still point to an old repo after renaming an organization.
  • Fixed an issue where the Workflows UI would fail to refresh data automatically.
  • Improved context loading times in cases when they could cause timeouts in the UI.
  • Fixed an issue where contexts would cause builds to return CIRCLE_BUG .

Help make this document better

This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.

Need support?

Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.

You can also visit our support site to find support articles, community forums, and training resources.