The GPU Linux machine images have been updated. Images for CUDA v10.2 and v11.1 are now available as ubuntu-1604-cuda-10.2:202012-01 and ubuntu-1604-cuda-11.1:202012-01.
You will now be able to access a granular view of your network transfer and storage usage on the Plan Usage page. Storage consists of stored artifacts, workspaces and caches that are core to the CircleCI platform experience, while network captures data transfer such as retrieving a cache in a subsequent job or uploading the job’s artifacts. This change allows you to have more visibility, granularity and control over usage. For more information, including self-serve strategies for optimization, please refer to the Managing Network and Storage Use page for more information.
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
If you change your default branch on GitHub, CircleCI will pick up that change and update the default branch for the project the next time you push some code. This is a bug fix – previously, changes to the default branch would not be picked up. This fix is retroactive and self-healing.
You can now add any combination of SSH key cipher / encoding. Specifically, we now support the ed25519 cipher, openssh encoding, and keys are not restricted to using the older (now non-default) PEM encoding. For more information, see the SSH keys guide in our docs.
When opening a job from the Legacy (jobs-based) run view, if the job has Pipeline data, it will now redirect from the legacy job view without pipeline data to the new UI view. Many cusomers use the legacy jobs-based view to find old SSH jobs, so this helps get to a page where they can cancel these jobs faster.
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
The runner feature is now available to customers on the Scale plan. Using runners, you can run private workloads using your own infrastructure while also using CircleCI’s cloud offering. Organizations can also use runners to build on specialized hardware. Learn more about runners in the Runner Overview doc.
The Scale plan is now available, providing improved support for enterprise organisations, including access to self-hosted runners, custom concurrency limits, our largest compute resouces and customizable annual billing options.
We have improved the error experience on the Pipelines Dashaboard by surfacing the main error and collapsing the details. This allows for quick scan accessibility, reduces visual clutter, and makes for a more consumable format instead of the full stack trace.
When a new organization has less than 20 pipeline runs within an project, a diagram is displayed to explain the concepts of job vs. workflow vs. pipeline.
The “Pipelines” link in the CircleCI app sidebar, which leads to the cross-project Pipelines view, is now called the “Dashboard” for a clearer route back to viewing all your runs in one place.
A selection of time filters have been added to the Insights workflow overview in the CircleCI app. You can now look at 24 hour, or 7/30/60/90 day time windows when reviewing your workflows Insights. Configurable time range is the most popular request on our ideas board, and we are excited to deliver a feature that gives you more granular control over your data.
CircleCI has partnered with Docker to ensure that our users can continue to access Docker Hub without rate limits. As of November 1st 2020, with few exceptions, CircleCI customers should not be impacted by any rate limits when pulling images from Docker Hub. Learn more in our Docker Authenticated Pulls doc.
You can now easily filter the projects you wish to view on the Insights dashboard page in the UI. This makes navigation easier, allowing you to easily find and view the projects you care about.
You can now follow and unfollow projects within your organization directly from the Pipelines dashboard. Previously all follow/unfollow options were only available through a redirect to the Add Projects page.
All organizations can now import environment variables from one project to another, as an alternative to using contexts to share them. This functionality was present on the old UI but initially not released on the new UI. All users can now access it by navigating to “Environment Variables” within project settings.
Performance plan credit refills will now be triggered at 2% and refills will be no smaller than 25,000 credits (or 25%). For more information see our billing FAQs.
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
Bitbucket announced the deprecation of its /2.0/teams and most /2.0/users endpoints and some response fields as part of its transition to their new “workspaces” domain model and API. Workspaces will replace teams; both of these concepts map directly to orgs in CircleCI. There should be no impact to customers.
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.
You can now toggle the auto-expand pipleines options on or off in the top-right corner of the pipelines dashboard. This is especially useful if you have pipelines containing many jobs, giving the advantage of keeping these pipelines collapsed, and if you have pipelines containing a small number of jobs you may prefer the auto-expand option.
The new Insights dashboard offers engineering teams access to actionable data for optimizing pipelines and getting even more out of CircleCI. With this feature, engineering teams will be better able to understand bottlenecks and identify optimization opportunities. Teams will be able to track workflow & job status, monitor duration and understand their pipeline throughput & mean time to recovery. Finally, Insights will serve to highlight the impact of more efficient CI/CD and to foster a better relationship with customers and provide a better experience. For more information, see the Using Insights guide.
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
The new Custom Plan will automatically track your usage, be able to provide real-time credit usage and balance information, and produce reports to accounting for invoicing. You will also be able to use user seats and be billed via credits for the usage.
Pipelines can now be triggered via the API for PRs (using PR number instead of branch), PR merge commits, and Forked PRs. This enables you to more easily validate new code from PRs. Triggering on PRs and PR merge commits offers the ability to better validate PRs in a programmatic way. Triggering pipelines on forked PRs is valuable for customers who have open source repositories that are frequently forked.
All Pipelines are now listed with the commit SHA in front of the commit message, which links directly to the commit in your VCS. This gives you a quick way to get to commits in your VCS from the Pipelines page.
We now offer a way for our user community to find all the best CI/CD config optimizations, migration guides/tools, and CircleCI docs, along with assets like CI configuration packages through CircleCI orbs and a newly designed Docker convenience image library, in one convenient place on our new developer hub. Check out the announcement here.
Multiple contexts can now be used in a Workflow. Previously, workflows were limited to having a single context. Instead of passing in a string to the context key in the config file, a list may be passed containing the contexts to be used in the workflow. This makes updates to contexts easier to manage and more secure.
Workflow Map connection lines are now straight and do not overlap. When you hover-over of a job, all dependencies from and to that job are highlighted.
The ‘credits available’ section of the Plan Overview in the UI has been updated to clarify some confusion around understanding credit balance. The bar display has been removed and the credits balance is now clearly shown.
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
The config error message shown when there is an empty config file on triggering a pipeline has been improved to both clearly state the problem, and provide a way to get back to project setup to add a config.
The button to manually add a config when starting a new project now reads “Use Existing Config”. Previously, this text read “Add Manually”. Through user research it was found that the new text directly encompasses many more use cases, including existing users with existing config ready to go.
The Branch and Commit message columns have been combined on the pipelines dashboard view of the new UI making the page easier to scan for the information you require.
The metadata section at the top of the Job page has been reworked to better group related concepts and include new labelling. This redesign makes it more clear which link is for which feature, especially for those not familiar with icons for branch, commit, PR etc.
The Pipelines page has been redesigned to merge the Project and Pipeline number columns together and make the font smaller across the whole page. This change allows you to see more pipelines on the dashboard without scrolling.
If you use Remote Docker in your Pipelines (setup_remote_docker) you now have the option of choosing Docker v19.03.12. For more information see the Discuss post. For usage information, and a full list of available versions see the Remote Docker Docs
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
New Ubuntu 16.04-based machine executor image, ubuntu-1604:202007-01 now available. For full details see the discuss post. For usage information see the Configuration Reference.
Waiting indicates the time spent preparing a job to run due to Docker image choice and CircleCI infrastructure time.
Queued indicates when you hit a concurrency plan limit, and your job isn’t running because other jobs in your organization are running first.
These two definitions were previously vice versa in the UI, which caused confusion due to discrepancies between usage in the UI and what most customers understood the terms to mean. We hope this change will avoid any confusion in future.
