CircleCI に関して最近行われた変更をお知らせします。RSS フィードはこちらから。
Xcode 13 Beta 4のイメージがmacOSリソースクラスで利用可能になりました。 このイメージはXcode 13 Beta 2を置き換えるものです。
詳細につきましては Image Manifest をご参照ください。
注意: このイメージにはNodeJSとRuby 2.5の利用者に対して、非互換を伴う変更の可能性を含んでいます。 詳細は Release Notes をご覧ください。
IP アドレスの範囲のオープン プレビューを開始し、有料プランをお使いのすべてのお客様にお試しいただけるようになりました。 この機能は、 IP アドレスに基づくアクセス制御が行われている環境に CircleCI からアクセスしたいお客様を念頭にデザインされています。 この機能では、 CircleCI のサービスが使用する IP アドレスのリストを提供します。 また、この機能を有効にした CircleCI のジョブから発生するネットワーク トラフィックは、リストにある IP アドレスのいずれかを使用するようになります。
なお、この機能では、当該機能を有効にしたジョブのネットワーク転送量に応じてクレジットの消費が発生します。 オープン プレビュー期間中は無料でお使いいただけますが、後日金額に関する詳細をお知らせしたうえで、機能が一般公開となるタイミングで有料化される予定です。
重要: この機能は、 Docker エグゼキューターを使用したジョブのみで使用可能です。 また、 remote_docker を使用するジョブでは利用できません。
機能の詳細については、 Discuss の投稿 (英語) をご参照ください。 また、 本機能に関する技術情報 (英語) も併せてご確認ください。
Q3 linux イメージに、最近見つかった PyEnv の問題を解決するためのパッチが適用されました。
この修正に関する詳細は、こちらの Discuss の投稿 をご参照ください。
四半期毎に更新しているCircleCIのLinuxマシンイメージについて、新しいイメージが利用可能となりました。 下記のとおりUbuntu 20.04のイメージが利用可能となっています。
7月の更新では、イメージに含まれているソフトウェアが更新されています。 マシンイメージの利用方法については machine executorドキュメント をご参照ください。
本アップデートの詳細については以下の Discuss post をご覧ください。
プラン利用状況 (Plan Usage) ページではワークスペースやキャッシュなどのオブジェクトを保存・復元した際のネットワーク転送量やストレージ使用量が見れるようになりました。
Xcodeの変更に対応して、以下の更新を行いました。
Xcode 12.5.1 が利用可能になりました。
Xcode 12.5.1が CircleCI の macOS リソースクラスで利用可能になりました。 このイメージは今後削除予定の Xcode 12.5.0に代わるもので、ジョブのリクエストは Xcode 12.5.1に変更されます。
Xcode 13 Beta 1 が利用可能になりました。
Xcode 13 Beta 1が CircleCIのmacOS リソースクラスで利用可能になりました。 このイメージを使うことで、開発者は iOS 15、tvOS 15、watchOS 8 のベータ版に対してアプリケーションのビルドとテストを行うことが可能です。
Xcode 13 Beta 2 が利用可能になりました。
Xcode 13 Beta 2 のイメージが macOS リソースクラスで利用可能になりました。 このイメージは Xcode 13 Beta 1を置き換えるものです。
これらの macOS の更新に関する詳細は、CircleCI のmacOS コンテナのページをご参照ください。
パイプラインページの上部右側の「Edit Config」ボタンの隣に、UIから新しいパイプラインを手動で実行するためのボタンが追加されました。 最初にブランチを選択する必要があり、そのブランチのHEADコミットでパイプラインが実行されます。
SSH ジョブの実行中にそのジョブページから離れた場合、そのジョブをキャンセルするために SSH ジョブページに戻るための方法は現在ありません。 レガシーコンテナプランをご利用の場合、キューにボトルネックが発生し、CircleCI サポートに連絡して問題を解決しなければならなくなる可能性があります。
今回のアップデートでは、「rerun-with-SSHジョブ」が実行されたジョブからのリンクが提供されるようになったため、より迅速にジョブをキャンセルできるようになりました。 なお、ジョブが実行中の場合のバージョンと、ジョブの実行が停止した場合のバージョンがあります。
全体的なユーザーエクスペリエンスを向上させるために、CircleCIのユーザーインターフェースに以下のアップデートを行いました。
ジョブおよびワークフローページでのタグ名の表示
Job and WorkflowページのDetailsセクションで、ExecutorとCommitのリストの間にタグ名が表示されるようになりました。
パイプラインページで失敗したテスト名の表示
失敗したテストがパイプラインページでジョブの配下に表示されるようになりました。 これにより、失敗してテストの詳細をより早く確認することができます。
テストのサマリーの表示を折りたたみ可能に
テスト結果が含まれたXMLファイルをシステムにアップロードする際、CircleCIはこれらのファイルを解析してテストサマリーを作成しますが、たまに大きくて見づらい結果が作成される場合があります。 今回のアップデートでは、出力セクションの左上にある三角の矢印をクリックすると、最小化されるので、次の問題に早く移動することができます。
ジョブの継続時間/終了時間のツールチップの改善
パイプライン、ワークフロー、ジョブページのツールチップが改善されました。 ジョブが実行された時間の上にカーソルを置くと、その情報がすぐに表示されるようになりました。 時間は以下の形式で表示されるようになりました。 “Started: Start: [Day of week], Month Day, Year at xx:xx:xx PM UTC-X.”
テスト機能を利用していない場合に、テストサマリーに青い点が表示されます
現在、テストのXMLメタデータをアップロードしていない場合、JobページのTest Summaryタブの横に小さな青い点が表示されます。 ジョブページでは、テストサマリーの機能を説明するCircleCIドキュメントへのリンクと図が表示されます。
パイプラインページでのステータスによるフィルタリング
パイプラインの一覧を表示する際に、パイプラインのステータス（失敗した、失敗していない）でフィルタリングできるようになりました。 これにより、ビルドをより早く見つけることができます。
ステップ出力に行番号を表示してリンクできるようになりました
ステップ出力ページを表示する際に、各ステップの行番号を表示できるようになりました。 また、このステップを他の人と共有したい場合は、特定の番号をハイライトしてクリックし、コピーすることができます。 この改善により、サポートを受け、ビルドの問題をより迅速に解決できるようになりました。
SSHで再実行した後にトーストが表示される
ジョブページで「rerun with SSH」をクリックすると、新しいSSHジョブが実行されます。 これには予想よりも少し時間がかかることがあります。 混乱を防ぐために、右下に「SSH job loading」と書かれた小さなトーストが表示されるようになりました。
これまでスケールプランのお客様にご提供していたプライベート Orbs が、すべての有料プランのお客様にも最大3つまでご利用頂けるようになりました。 スケールプランのお客様は、引き続きプライベート Orbs を無制限でご利用いただけます。
2年前にリリースしたCircleCI Orbs はユーザーの開発プロセス全体の簡素化に貢献してきました。 しかし、多くの開発者から、複数のプロジェクトでの設定を非公開にし、組織内だけで共有したいというご要望を頂いていました。 プライベート Orbs では、Orbs を組織内だけで共有することが可能です。
プライベート Orbs の詳細についてはこちらのドキュメントをご覧ください。
Big SurでビルドされたXcode 12.5のイメージが、CircleCIのすべてのmacOSリソースで利用可能になりました。 これにより、最新のiOS、tvOS、watchOSのバージョンに対応したアプリケーションを構築することができます。
詳細については、次のdiscussの記事を参照してください。 こちらからご覧いただけます。
CircleCIのリモートDockerでは、新しくDocker（v20.10.6）が利用可能になりました。
このバージョンや他のリモートDockerのバージョンについては、こちらをご参照ください。
プレビュー期間を経て、CircleCI Cloud にて Arm リソースを一般公開しました。 すべてのプランのユーザは、arm.medium リソースにアクセスできます（Free プランと OSS プランを含む）。 arm.large リソースは、Performance、Scale、カスタムプランのお客様が利用できます。
CircleCI の Arm リソースの詳細については、こちらの CircleCI Arm ドキュメントを参照してください。
クレジットを使用していない請求期間 (Billing Period) を選択した場合に表示される空の状態の UI を改善しました。 CircleCI を最近使用していない場合や、CircleCI を使い始めた場合に前述の空の状態のUIが表示されます。
これまでは、別の請求期間を選択するためにはページを更新する必要があるというメッセージが表示されていました。 改善後は、UI 内で選択した請求期間を変更するオプションをそのまま利用できます。
サンプルコンフィグテンプレートにいくつかの変更を加えました。
最も人気のある5つのサンプルコンフィグテンプレート（.NET, Android, Maven (Java), Node, Python）が更新されました。 アップデートには以下が含まれます。
最後に、サンプルコンフィグをドロップダウンではなくモーダルに表示することで、見つけやすく、アクセスしやすいようになりました。 カードのレイアウトが改善され、コンテンツが追加されたことで、サンプルコンフィグを簡単に選択できるようになりました。
コンフィグに、pattern(条件)とvalue(値)の2つのパラメータを持つmapを利用する、matchesという新しいロジックステートメントが追加されました。 値が条件に正規表現でマッチした場合、値はtrueとして返されます。 このようにwhenステートメントで正規表現のマッチングを行うことで、ブランチやタグに基づいて個々のステップやワークフロー全体をフィルタリングしたいお客様は、使用したいロジックに合わせてより一貫した方法でフィルタリングを行うことができます。
詳細については、ドキュメント「CircleCI Configuration Reference」を参照してください。
この機能により以下のフィーチャーリクエストが解決されています。:
プラン利用状況 (Plan Usage) ページのパフォーマンスが大幅に改善され、ページの読み込み時間が短縮されました。 これにより、ご利用の多いお客様は、ページがタイムアウトすることなくこのページにアクセスし、読み込むことがでるようになります。
Windows イメージの一部のユーザーにおいて、近日、nuget restore を実行する前に choco install を実行すると、nuget.org パッケージソースからのパッケージのダウンロードに失敗するという問題がありました。
この問題を解決するために、パッケージソースとしてnuget.org が設定された user-wide の NuGet 設定ファイルを追加し、Windows のイメージを更新しました。
このワークアラウンドについては、こちらの Discuss 記事を参照してください。
これまではインサイトのダッシュボードで得られる情報が単一のブランチでスコープされていました。 本日からプロジェクト全体のブランチにおけるインサイトデータにアクセスでき、ワークフローやジョブのパフォーマンスをより簡単に把握できるようになりました。
CircleCI ジョブを使用してパイプラインのパラメータや YAML コンフィグを生成するためのセットアップ・ワークフローによる動的コンフィグ機能を一般公開しました。 これらの生成されたパラメータとコンフィグは既存のパイプラインに付加することで、ランタイムの入力に基づいてコンフィグを動的に生成することができます。 この機能は既存のワークフロー/ジョブで既に使用されているため、Orbsはセットアップ・ワークフローの一部として使用することができ、異なるユースケースのためにOrbsを作成することで、様々なユースケースをカバーすることが可能になります。
セットアップ・ワークフローによって可能になった具体的なユースケースのひとつに、パス・フィルタリングがあります。 これは、どのファイルが変更されたか（スクリプト内の一連のGit操作によって特定される）に基づいて、どのワークフローを実行すべきかを決定するものです。 これは、モノレポを使用している場合に重要な機能であり、ビルドプロセスを最適化できます。 また、パスフィルタリングを有効にするためのOrbsもあります。
Dynamic Configurations の詳細については、こちらの製品発表をご覧ください。
また、この機能についてはこちらのドキュメントをご覧ください。
Microsoftからの最新のバグ修正とセキュリティ修正が含まれている4月分のパッチがWindows Executorのイメージに適用されました。
インサイトのランディングページが更新され、ユーザーに組織の各プロジェクトによるパフォーマンスの細かい概要を提供できるようになりました。 今回のアップデートでは、ランディングページを簡素化し、大規模な組織でもプロジェクトごとのパフォーマンスが簡単に確認できるようになりました。
また、各プロジェクトに対するデータをより深く調査できるプロジェクト詳細ダッシュボードを追加しました。 プロジェクト詳細ダッシュボードでは、マルチブランチフィルタリングがサポートされ、ワークフローとブランチによる詳細な分析が可能になりました。
ユーザーがインサイトのメトリック用語集にアクセスできるようになりました。 この機能は計算の方法を含め、インサイトのメトリックの詳細な定義と例を提供し、インサイトダッシュボードが最大限に活用できます。 また、ドキュメントにインサイト専用のセクションがあり、詳細なインサイトのコンテンツによりアクセスしやすくなりました。
これまではCircleCIのorbのバージョンバッジは、社内のCPEエンジニアが管理するサービスで提供されるデータ利用し、shields.ioで作成していました。 このプロセスはCircleCIが公式に管理しているものではありませんでしたが、今回のアップデートにより、Orbバージョンのバッジ生成プロセス全体がCircleCIに集約されます。
この更新の詳細に関してはOrb Version Badgeのdiscussの投稿を参照してください。
Note: このアップデートは少し前からご利用になれましたが、状況を慎重に監視するために特に発表はしませんでした。
セットアップ ワークフローのプレビュー版が公開されました。セットアップ ワークフローを有効にする方法についてはこちらの Discuss Post (原文 日本語参考訳) をご覧ください。
セットアップ ワークフローによって、 CircleCI のパイプラインのパラメータや構成を CircleCI 上で生成することができます。これにより、元のパイプラインに付加するかたちで、動的に構成したパラメータ・構成に基づくパイプラインを実行することができます。セットアップ ワークフローは既存のワークフロー・ジョブに準じた方法で定義できるため、セットアップ ワークフローの内部で Orbs を使用することも可能です。 orbs の有効活用により、より多くのコンフィグ動的生成のシナリオをパッケージ化することが可能です。
セットアップ ワークフローの特筆すべき使用例はパス フィルタリングです。パス フィルタリングにより、ファイル変更の有無に応じてワークフローの動作可否を決定することができます (このときファイル変更有無の検出には Git コマンドを軸に使用したスクリプトが使われます)。この機能は特にモノレポ構成となっているプロジェクトでのビルド プロセスの最適化に効果を発揮します。パス フィルタリングの実装は CircleCI 公式の orb により簡略化することができます。
新しい Android マシン イメージが追加されました。 ネストされた仮想化 (nested VM) と x86 エミュレータの実行がサポートされました。 この新しいイメージにより、CircleCI 上で Android エミュレータベースの UI テストや、ネストされた仮想化を必要とする他のタイプのビルドを実行することが可能となりました。
この Android マシン イメージの詳細については、この新しいイメージを説明した Discuss 記事を参照してください。
また、お客様からのご要望や問題点を取り上げた以下のフィーチャー リクエストもご参照ください。
テスト インサイト（Test Insights）は、すべてのクラウドのお客様に Open Preview で提供されています。 テスト インサイトは、インサイト機能の中でも最も要望の多かった機能であり、ユーザーの皆様にこの機能をお届けできることを大変嬉しく思います。 テスト インサイトでは、最近実行したテストのパフォーマンスを分析し、テストを最適化するための新たな機会を特定することができるようになります。
テスト インサイトのプレビュー版へのアクセス方法については、こちらの Discussion をご参照ください。
コンテキスト REST API を公開しました。 この API はシークレットローテーションを可能にするため、かつ、RESTful なパブリック API に移行するために構築されました。 CircleCI API の可用性を高めるため、以下の改善を行いました。
プラン利用状況ページのサマリーのデザインを更新しました。 表示される詳細は、各プランタイプで利用可能な機能に基づいています。 これにより、異なるプランタイプ間でデザインが統一され、より一貫した操作が可能になります。
定期的なアップデートの一環として、リモート Docker マシンがストレージドライバとして overlay2 を使用するように変更しました。 この変更により、Docker Layer Caching (DLC) を使用する一部のジョブが、Docker マルチステージビルドの COPY ステップで失敗する原因となりました。 この問題は、DLC ボリュームのローテーションに伴って自動的に解決されるはずですが、それでも問題が解決しない場合は、サポートにご連絡ください。
お客様へのサポート及び、セキュリティの向上のため、CircleCI のドキュメントにAPI トークンに関するベストプラクティスが追加されました。
Personal と Project API トークンローテーションに関する詳細な情報はこちらをご覧ください。
お客様へのサポート及び、セキュリティの向上のため、環境変数のローテーションとそのセキュリティ上の重要性が説明されている CircleCI のドキュメントが更新されました。 また、このドキュメントの更新には、環境変数のローテーションを行う方法を追加しました。
これらの変更に関する詳細な情報はこちらをご覧ください。
Trends data is now available at the organization level. Additionally, trends for the Mean Time To Recovery (MTTR), Throughput, and Duration metrics have been added. As a reminder, Trends provides relative benchmarks for the 24-hour, 7-day, and 30-day time windows against previous time windows.
When support needs to impersonate your account to troubleshoot an issue you reported, you will now receive an email to notify you they are doing so.
You can now view your configuration in YAML with a side-by-side JSON view, enabling you to solve your configuration in a more familiar language.
The most recent images for the Windows executor now include the .NET Core SDK 3.1. This means you will now have access to the latest version out-of-the-box, as the old Windows version has been deprecated.
CircleCI’s in-app configuration editor makes it quick and easy to resolve errors and write your config file. Features include:
This feature can be conveniently accessed upon project set up, on your dashboard when a project and branch are chosen, in the More Menu under Configuration File, and in-line when your pipeline or job fails.
Today we are enabling private orbs for our Scale customers.
Two years ago, open-source orbs were launched, helping users to simplify their entire development process. However, we also knew that many developers wanted to privately share configurations across multiple projects, exclusively within their own organization. Private orbs enable users to create orbs specific to their organization without exposing sensitive data or content to users outside of that organization.
You may now create, publish, and update private orbs via your organization’s admin. These private orbs will be restricted to, and accessible by, all users within the organization, and can be listed and imported into a config.yml file directly from the CircleCI CLI.
For more information about private orbs, refer to the Circle CI orbs documentation, which can be found here.
It has been observed that a barrier to activation and source of pain for users is partially due to frustrations with using YAML. By experimenting with a side-by-side JSON view, an increase of 8.35% was observed in org activation, 10.75% in org activation within its first 7 days, and a 3.97% decrease in the percentage of pipelines that were run with errors. This indicates that organizations are learning from this feature as they problem solve config and graduate into the platform.
Two new versions of Remote Docker (v19.03.14 and v20.10.2) have been released and are now available for use.
You will now see a faster checkout step in your CircleCI jobs. The built-in checkout step now does a git clone without checkout, followed by checking out the branch (overwriting existing) at the SHA received from the VCS provider. In addition to speeding up the checkouts, a number of Git checkout-related issues have been resolved, resulting in improved reliability of the checkout step.
We have introduced a few new tooltips to improve your experience on the platform:
On the right side of the Job page, jobs now specify whether the job was split up into parallel runs. If a job was split, you are able to see what level of parallelism was used out of how much was available. Previously, this tooltip only displayed the browser’s title attribute, but now you will be able to instantly find information on increasing parallelism.
On the right side of the Pipelines page, there are three different workflow actions: rerun, rerun from failed, and cancel. An instant tooltip is now displayed to help you learn how to quickly rerun pipelines.
When you navigate to the Tests tab of a job page with failing tests, the output boxes used to have a light grey background with black text. These output boxes now have a black background with white text to match the output boxes in the Steps tab. This change addresses requests from users who dislike reading long outputs on lighter backgrounds.
On a project-specific Pipelines page, there is now a link where you can invite a new team member to the project. When you click this button, a modal pops-up where you can copy a link to the Project page. Any team member who then opens the copied link will auto-follow the project. This feature helps you to get more of your teammates onboard and building with you on CircleCI.
As a part of a regular update, we are rolling out a change to the filesystem in the machines that all Docker executor jobs run on. The filesystem the Docker jobs use will now be XFS with the Overlay2 storage driver. Initial metrics of this change suggest faster and more reliable build times. You will not need to make any changes to take advantage of this update.
You can read more about this update in the following post:
We have initiated a preview of hosted Arm resources on CircleCI. Arm is an architecture that is quickly gaining traction for server workloads. Organizations choose Arm because of its faster performance, which results in faster workloads and significant cost savings compared to x86-based architectures. An essential piece of migrating workloads to Arm is having Arm support in your CI system. If you are on a usage-based plan, including the Free plan, you may request access to the Arm preview. We are making two arm64 resources available: arm.medium and arm.large.
To request access, customers must fill out an access form that is linked in the preview docs below.
The software for the standard Linux Ubuntu 16.04 and 20.04 images has been upgraded to support amd64 and arm64 images. The ARM image specifically is still under preview with overall CircleCI ARM support. The standard images are GA releases.
If you have configurations set up to collect test metadata, you will now have an easier time understanding what tests may have failed. On each Job page with a failed test, there is now a box above the steps/tests/artifacts tabs with a summary of how many tests failed, how many tests ran, and links to the names of each test that failed. The links jump to the output of the test failure further down the page. There is also a copy button to the right of each name if you would like to copy the name and rerun it in your personal IDE.
You can now navigate to your Config Editor and Project Settings from the Insights dashboard. Previously, you would have had to leave Insights and navigate to the dashboard/pipelines tab to access these settings. This update provides easier access to these settings.
You can now access Trends data on the Job Insights page. As a reminder, Trends provides relative benchmarks for the 24-hour, 7-day, and 30-day time windows against previous time windows.
Insights now persists the current branch when navigating from the pipelines or workflow runs pages. The dashboard displays the current/selected branch instead of defaulting to main. Similarly, on the Insights dashboard, changing workflows on a given branch no longer results in the branch reverting to main.
Concurrency and parallelism limits have been increased from 40x to 80x for all new and existing Performance Plan customers.
Raw metric values are often difficult to interpret and perform actions on without context. The Trends feature provides additional context presenting a relative benchmark against previous performance, enabling you to retrieve more data and gain additional insight into your data. The workflow details page supports trends for the 24-hour, 7-day, and 30-day time windows.
You may now export the jobs table from the Insights dashboard as a CSV file. Downloaded reports can be used to run additional offline analysis or share with coworkers.
You will now be unable to add SSH DSA keys to projects. Please note that SSH has defaulted to RSA keys for a long period of time and DSA keys have been deprecated. The error message that appears when trying to add a key of this type is unsupported key type: ssh-dss. If you experience this error, please use a more modern supported key type (RSA, ECDSA etc).
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 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.
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.
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.
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.
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.
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.
A new PHP convenience image has been published. For more infomation see our discuss post.
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.
Job links in the UI are now blue rather than black to make naviagation between pipeline elements easier.
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.
New Ubuntu 16.04 and 20.04 Linux machine images are now available. For more information, and usage examples, see our discuss post.
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.
Configuration validation is now available in the in-app config editor to visually show config status at the point of adding a config to your project.
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.
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.
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.
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.
Fixed a bug that was causing previous macOS trials to show as $0 plans on the Plan Overview page. Old trials are no longer visible in the UI.
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.
Child orgs now get premium features, including resource class allowance and DLC, from the parent org when plans are shared.
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.
Commit messages are now displayed along with commit author on the Job page in the New UI.
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 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.
Non-admins can now see Plan Overview and Usage pages in the new UI.
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
Next-gen Elixir docker image now available. For full details see the discuss post.
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.
You can now commit config directly from the Project Set-Up page to your repo with 1-click. The same config can also be downloaded and committed manually if preferred.
Container cgroup limits are now visible when using the Docker executor. This means that container-aware build tooling will now correctly detect the number of CPUs and amount of RAM available to the job.
You can also view these numbers directly by looking at the files in the /sys/fs/cgroup directory:
/sys/fs/cgroup/cpu/cpu.shares/sys/fs/cgroup/cpu/cpu.cfs_quota_us/sys/fs/cgroup/cpu/cpu.cfs_period_us/sys/fs/cgroup/memory/memory.limit_in_bytesThe Plan Usage page in the new UI now includes a Compute tab, showing compute minutes and credits by executor type. You can also further filter the breakdown by projects. MacOS container plan users will also see overages within this tab.
If you are not currently on a usage plan, this page will show compute usage by credit and user to give an indication of what to expect on the usage plan.
A link to the changelog is now on the Help menu, accessible from any core-app page.
Favicons for CircleCI job pages now reflect the status of the job. The icon becomes red for a failed job, green for success, and blue for still running.
Previously, queue and wait times were hidden behind an information icon hoover-over. They are now in their own section in the Job Details header. User-research showed these items were hard to find and folks did not like them being hidden.
The new Plan overview page includes improved visualisations for credit usage, user seats and upgrade options. Access the Plan overview from the new UI sidebar.
image: cimg/rust:1.43.0
This is a direct replacement for the legacy CircleCI Rust image (circleci/rust). You can find this image on Docker Hub, and the source code & documentation on GitHub.
image: cimg/ruby:2.6.5
This is a direct replacement for the legacy CircleCI Ruby image (circleci/ruby). You can find this image on Docker Hub, and the source code & documentation on GitHub.
Docker v19.03.8 now available via Remote Docker (setup_remote_docker). Read more in the Discuss post and in the Docs Building Docker Images guide.
image: cimg/openjdk:14.0
This is a direct replacement for the legacy CircleCI OpenJDK image (circleci/openjdk). You can find this image on Docker Hub, and the source code & documentation on GitHub.
The new logic constructs allow for more powerful compilation-time decisions about which work to perform. Read more on our Discuss post.
image: cimg/go:1.13
This is a direct replacement for the legacy CircleCI Go image (circleci/golang). You can find this image on Docker Hub, and the source code & documentation on GitHub.
image: cimg/node:12.16
This is a direct replacement for the legacy CircleCI Node image (circleci/node). You can find this image on Docker Hub, and the source code & documentation on GitHub.
The default branch, usually master, is now pinned to the top of the branch selector list, as well as below in alphabetical order to prevent it being missed.
You can now type to search for the project you need in the project selection dropdown on the Pipelines page.
Roll out of the Share and Transfer Plan settings page has started in the new UI, making it easier for you to share, unshare and transfer plans.
You can now type to search for the branch you need on the pipelines page.
There is now a “help” icon and button on the main navigation of the new UI. When expanded, this menu includes links to Docs, Discuss, Support, Premium Support, Orbs and Feature requests.
The new UI now includes a link to the status site. In case of incidents, this icon will update to yellow (degraded), orange (parial outage) or red (outage).
You can now approve jobs with API v2. The new endpoint is POST /api/v2/workflow/:workflow-id/approve/:approval-request-id. The approval request id is the ID of a pending approval job, which will also be returned as an approval_request_id on approval jobs returned by the API. For more information see the API v2 docs.
The config editor available during project setup now visually display mistakes and offers suggestions specific to CircleCI’s configuration schema.
Xcode 11.5 Beta 1 image has been released. Read more here.
Colorized loading of step output has returned to the new UI on the Job Details page up to 6000 ANSI words.
A new Machine executor image ubuntu-1604:201903-01 is now availabe, with Docker 19.03 pre-installed. See this Discuss post for the list of the versions of core software also available in this image. Check out the Machine executor docs for instructions on how to use this image with the Machine executor.
Slack has been a powerful way for orgs to get status updates and custom alerts. We’ve brought it back in the new UI under Project Settings to aid users to solve their problems more efficiently while remaining in their Slack workflow.
The Test Summary tab on the Job Details page in the New UI now displays green when tests pass, and red for failures. The number of tests run, or number of failed tests is also displayed.
When viewing the Pipelines page, the most recent pipeline and any failed pipelines will be auto expanded to show the jobs that ran. This gives a quicker route to accessing job step output.
Previously, the number of parallel runs in use was displayed, now both this and the maximum available are shown. You can also hover over the adjacent information icon for further information.
Xcode 11.4 image has been updated. Read more [here]https://discuss.circleci.com/t/xcode-11-4-updated-image/35474).
We have decreased the first meaningful paint time down to 1.96 seconds and improved load-time perception for the job detail page in the new UI.
We are now making a RAM disk available for our Docker executor at /mnt/ramdisk. This has the potential to significantly speed up certain types of build. For usage, please check the docs.
All non-HTML build artifacts on CircleCI now redirect to short-lived pre-signed cloud storage URLs. This change has been made to improve the performance of our artifacts hosting.
If you are using a web browser to view HTML resources, such as test/coverage reports or download tarballs/zip files, you will not need to change anything.
If you are using curl or another HTTP client that does not follow redirects by default, you will need to enable redirect support. For curl, you will need to add an -L flag. Please check the docs for more information.
You can now manually unblock an approval job from the Pipelines List page in the new UI. Originally this functionality was only availble from the Workflows map. Read more about approval jobs here.
The new matrix stanza allows you to run a parameterized job multiple times with different arguments. Read more about matrix jobs here.
Xcode 11.4 (GM) image is released. Read more here.
If any of your scheduled workflows become unscheduled for any reason, you will now be notified by email.
URLs for onboarding pages have been consolidated for security and improved usability. They now follow this structure:
https://app.circleci.com/projectshttps://app.circleci.com/projects/project-dashboard/:vcs/:org-name:/https://app.circleci.com/projects/project-setup/:vcs/:org-name/:project-nameURLs for Settings pages have been consolidated for security and improved usability. They now follow this structure:
https://app.circleci.com/settings/userhttps://app.circleci.com/settings/project/:vcs/:org-name/:project-namehttps://app.circleci.com/settings/organization/:vcs/:org-nameScheduled workflows are now available as piplines in both the new UI, and the API.
Autocommit is a new feature that allows you to commit a sample language-specific config direct to a new branch on your repo when adding a project, making it even quicker to start building on CircleCI. You can also edit the config prior to committing. These features are in addition to the option to manually commit a config file.
When adding a new project to CircleCI, the project dashboard sidebar now dynamically displays language-specific docs and guides to help you get started quickly and get the most out of the service.
Wait and queue times can now be accessed for each job in the new UI. Hover over the i next to the Duration at the top of the job details page, and the wait time and queue time appear as a tooltip. This information has been added to the new UI to make it easier to get information on edge-case failures in your pipelines.
The new UI URL sub-domain structure has been updated for improved security and usability. The new structure makes it easier for developers to interact with URLs like breadcrumb items.
Read more in our Xcode 11.4 Beta 3 image announcement.
The Legacy Jobs view in the new UI provides an overview for all jobs, regardless of whether they have pipeline processing enabled. We are aiming to move all customers over to pipeline processing, and this view has been added to provide the information you need for all projects during this transition period. Access the Legacy Jobs view at the end of the Pipelines List page.
Read the March update on CircleCI Docker Convenience Images here.
CircleCI is making changes for a stricter permissions access. Going forward only GitHub administrators will be able to view and access the following pages in the CircleCI application:
Note: This does not affect Bitbucket users.
Read more and give feedback on our Discuss post.
You can now show, create, delete and list Contexts via the CircleCI CLI. Run circleci update to get access to this new Context functionality.
Project and branch names are now included in the navigational breadcrumb trail in the new UI, placing essential pipeline information in view and making it quicker and easier to navigate to the pages you need.
The way build artifacts are hosted is changing to improve performance. Read our Discuss post for further details.
From March 9, 2020, CircleCI will begin to enable pipelines for all projects. A pipeline contains all of the workflows (and the jobs inside those workflows) that CircleCI runs after a trigger on your project. A pipeline can be triggered by a pull request, a commit, or even an API call. Read more on our Discuss post.
As we build the new UI, faster page-load is important to us. We initially built the Step Output section to load with react-virtualized, meaning that only the visible rows were rendered. This allowed us to show colorized output with an even faster load/scrolling time than the old UI. In theory it was brilliant, in practice it broke the ability to use native browser search tools like CMD+F to find specific words before or after the rendered text. During user research, we watched many CircleCI users attempt to CMD+F in the Step Output, and not find what we were looking for. As a result we pulled out react-virtualized and enhanced colorized output from the step output. Color we can compromise on, usability we cannot.
Resource type and class is now displayed in the new UI for each job. This helps customers optimize pipelines, debug runs that fail due to lack of resources, and identify projects that could build faster with a different resource class.
Get job run data, including status, credits, and duration, for each individual job within a workflow. More info here.
The redesigned Project Settings page is now available in the new UI. Change SSH keys, Environment variables, API permissions, JIRA integrations, and more.
Next-generation Go image, and new base image are now stable. Read more on the Discuss post.
The following resource classes are now available to customers on the Performance plan: XL and 2XL for the Machine executor, and 2XL for the Windows executor.
With this update, CircleCI users can deploy directly from their CI/CD pipeline to Windows containers. Read Google’s announcement here.
Visit the GKE orb page for more information.
Customers on the Performance plan and macOS plan can now build using Xcode 11.3.1. See our iOS documentation for the details of software installed in this new image.
The Organization Settings page in the New UI is now live. Organization Settings include contexts, environment variables, security permissions, and VCS integrations.
The latest commit message for each pipline is now visible on the Pipelines overview page to make identification easier.
API v2 enables new functionality, such as triggering and retrieving pipelines and workflows via the API. Read more about it in our blog post.
You can now page through older Pipelines using the See More button at the bottom of the Pipelines Page in the new UI. Up until now only the last 20 Pipelines were available. Please note that due to API contraints, paging through older Pipelines will disable the live update of currently running Pipelines on the page.
Branch and “My Pipelines” filter options are now available in the new UI. Both are easily accessible at the top of the Pipelines page. Filter options now include:
You can now cancel and rerun workflows from the Workflow Detail page. Previously this functionality was only available from the Job Detail page. This change was made after data analysis indicated that most users were rerunning workflows from the workflow level rather than the job level on the old UI.
We have fixed a bug that was preventing folks on Performance Plans from transfering ownership to another plan. Please note only org admins can transfer plans.
Manual approval of hold jobs is now fully functional in the new UI. To approve a job, click the name of your workflow from either the Job Detail page breadcrumb, or the Pipelines List page to navigate to the Workflow Map. You will see the approval job has a purple status icon. Click the job and a button will pop-up to confirm approval.
You can now try out Pipelines on an individual branch before switching your whole project over. There are two ways to try this — 1) If you use config version 2.1 your run will now automatically trigger a pipeline. 2) If you want to keep your version 2 config you can use a new key pipelines under experimental in your config.yml it would look like the following:
experimental:
pipelines: true
Version 2 config with pipelines enabled will now automatically have the CIRCLE_COMPARE_URL injected into the job configuration. Previously, if you referenced CIRCLE_COMPARE_URL in a version 2 config, then turned on pipelines, it would disappear. This fixes that issue. For version 2.1 config we do not automatically inject CIRCLE_COMPARE_URL. Instead, we have exposed metadata about the pipeline for you to use more granularly. Mosts users end up parsing out CIRCLE_COMPARE_URL, so instead we did that work for you. In version 2.1 config you can now do the following:
version: 2.1
jobs:
my-job:
environment:
CIRCLE_COMPARE_URL: << pipeline.project.git_url >>/compare/<< pipeline.git.base_revision >>..<<pipeline.git.revision>>
New pipeline metadata values can be referenced in your 2.1 configuration. Unlike CIRCLE_ environment values, these pipeline values are available at config processing time, so you could choose to use them in your configuration superstructure outside of jobs. For example, you could use pipeline values as strings for your working_directory or your image key under a job. Read more in our Pipeline Variables guide.
The workflows graph is now available in the new UI, with improvements in the way job connectivity is displayed, compared to the old workflows graph. This core feature displays a visual representation of how jobs fit together within your workflow.
All rerun options - Rerun Workflow, Rerun Workflow from Failed, and Rerun Job with SSH – are now available from the Job Details page in the new UI.
Secret masking has now been enabled for 100% of our customers. To read more about the new secret masking feature, read our blog post.
You can now access your configuration files, both pre-processing and post-processing, from the new UI, when opted in. The config file links are available from both the Job Details page at the top right, and the Pipelines list page via the 3-dot drop-down menu.
After loads of great feedback we have determined our Job Details page in the new UI now adds far more value than the old UI equivalent. We are beginning to automatically opt-in customers who will benefit most from the new view – those who primarily use the Job Details page (as opposed to needing the Workflows Map). A welcome message will be displayed on arrival and you can opt-out at any time.
We’ve released our first macOS 10.15 Catalina image along with Xcode 11.2 Beta 2. Read our discuss post for more on highlights and usage.
You will soon be able to access User Settings from within the new UI experience when opted in. Everyone will have access by the end of next week. Just click on your profile icon at the bottom of the left-hand panel to view User Settings.
CircleCI’s new usage-based pricing scheme expands your capabilities to optimize and scale CI/CD pipelines. Eliminate queuing, get full access to resources, optimize your compute power, while only paying for what you use. Read about our new pricing model and learn more about usage-based pricing in our blog post.
If you are running OSS builds, you may continue doing so, even if all user seats are filled.
If you are on the Performance Plan, you will start to see refill amounts changing at the next billing date. Based on feedback about a high number of charges for refills, the refill amount has been increased from 10% to 25%. The refill will automatically be attempted when the plan reaches 10% of credits remaining.
If you are on a CircleCI Free plan, you may now access the Windows compute type. To access Windows, add the specification in your .circleci/config.yml file. Refer to the Hello World Windows document for instructions.
To try it out, Enable Pipelines in your Project Settings and then click the opt-in banner available on any Job Detail page. We are actively monitoring feedback and bug reports through a poll that appears in the app. The data and commentary we receive directly impacts what we build next, so opt-in to be a part of making CircleCI better!
Rerun with SSH, the top new requested feature from in-app feedback from new UI users, is now available. We are rolling out this feature slowly to monitor for bugs, but we are excited to honor the feedback.
Customers on the Performance plan and macOS plan can now build using Xcode 11.0 (as of Sep 20th) and Xcode 11.1 (as of Sep 26th). Please see our iOS documentation for the details of software installed in these new images.
Cancel Button in the New UI For users opted-in to the New UI experience, jobs can now be cancelled from the Job Detail page.
New Navigation System in the New UI Previously, the Pipelines page was only available from the breadcrumb on the Jobs page, or through the URL. A new central navigation system now appears on the left-hand side of the screen with a Projects menu on the Pipelines page.
To unlist your published orbs from the registry, use the new circleci orb unlist CLI command. For details, refer to the help page. Unlisted orbs remain world-readable when referenced by name but will not appear in the search results of the orb registry. Unlisted orbs can be listed again using the circleci orb unlist <namespace/orb> false command.
For Free plans, the Plan Usage page has been updated to provide you with more visibility into how you’re using the product. The total number of build minutes and users now appears on the along with the breakdown of usage by projects and a list of users for each month.
Build minutes and corresponding credits were also added to the page to help you understand your credit usage if you choose to upgrade to the Performance plan.
We know how painful it is to have delays in Xcode image availability. We’ve been working to reduce the often 2-3 week delay as we validate security, availability, and performance in our release process. We are now down to under 3 days on the last four releases and expect this trend to continue.
You can now find Artifacts the new UI Job Details page. We started with a flat list after numerous customer interviews. It’s no surprise that “find” is our friend. We will eventually build a search bar to filter artifacts - but hey, cntrl-f is easy. Please give it a whirl and share your feedback.
Select users with pipelines enabled on their projects will see a banner on the Job Details page that enables opt-in to the experimental new UI as it is being built. This new UI includes the following:
Read more information in the Discuss post.
CircleCI customers on Performance plans can now run jobs on Windows Server 2019 with popular dependencies— .NET support, Visual Studio, Windows SDK, Docker for Windows, as well as cross-platform workspaces, and caches. Learn more about Windows support here.
Invoiced Linux container plan customers will see their plan properly listed as Manually Invoiced on the Plan Overview page.
When no additional user seats are left in your plan, new users will be blocked from initiating jobs.
The Plan Usage page has also been updated to include Unregistered user (previously Guest user) and Scheduled workflow in your user list if you are initiating jobs usging scheduled workflows.
FREE minutes shift to 250/week
Customers on FREE plans will notice a change in how their monthly minutes are allocated. Customers will retain 1,000 FREE minutes per month and will receive them in increments of 250 minutes per week. This will allow customers to budget credits in a more manageable way while aligning with a Mon - Fri work week.
Performance Plan customers will now be alerted when they have used up their user seat allotment. These customers will need to update their subscription to allow all of their team members to use CircleCI.
CircleCI enables you to restrict environment variables at run time by adding security groups to contexts. Security groups are definied as GitHub teams. After a security group is added to a context, only members of that security group who are also CircleCI users may access or use the environment variables of the context. See the Restricting a Context documentation for details.
In an effort to improve incident reporting, CircleCI replaced status banners with a gauge icon in the application.
Our goal is to provide you with a better understanding of your pipeline’s current system health which includes CircleCI infrastructure and common external dependencies. Before, banners hid root cause and communicated issues to everyone even though the incident was relevant to few. Now, a gauge icon will give you a dynamic view into general infrastructure health and fast access to https://status.circleci.com for deeper details.
CircleCI uses 3rd-party tracking pixels to analyze traffic and optimize our marketing efforts (read our privacy policy to learn more). You can now disable these pixels within the CircleCI application by opting out. To do this, click the drop down menu under your picture and follow User Settings > Privacy & Security to check the opt-out box.
An error message is now returned if adding an SSH key fails.
Projects are no longer checked by default on the Getting Started page to avoid causing all unintended projects to start building.
Orbs are now licensed out from CircleCI to users under the MIT open-source license agreement. Refer to the Licensing page of the Orbs Registry for details.
For customers with many branches, the branch picker will now load only a subset of branches to improve performance.
Insights tab will now load properly when visiting from jobs, workflows, or settings tabs.
For customers with large logs, there’s now a way to open the log file in a separate browser in addition to to downloading the file.
It is now possible to sort the list of orbs according to their usage by running the circleci orb list --sort command.
The usage warning banner for Free users has been updated to exclude build minutes from OSS projects.
The My Branches button on the Jobs or Workflows pages has been fixed to display all relevant branches.
Orb elements can now be composed directly with elements of other orbs. For example, you can now have an orb that looks like the following:
orbs:
some-orb: some-ns/some-orb@volatile
executors:
my-executor: some-orb/their-executor
commands:
my-command: some-orb/their-command
jobs:
my-job: some-orb/their-job
another-job:
executor: my-executor
steps:
- my-command
param1: "hello"
.circleci/config.yml file:macos:
xcode: 10.1.0
Orbs are packages of CircleCI configuration shared across projects. Orbs help you simplify YAML configuration, enable you to build on top of CircleCI, and support sharing of standardized configurations across your projects.
This release provides you with access to certified orbs for AWS CodeDeploy, Rollbar, Artifactory, CodeCov, Heroku, Slack and more. You can also create and publish your own orbs using the CircleCI CLI. Refer to the CircleCI Orbs Registry for the complete list of certified orbs.
To learn about using and creating orbs, see the following documentation:
The Documentation search bar has been completely redesigned and improved to provide a full page of aggregate results, see CircleCI Docs.
The Org Switcher was updated to fix a display issue that caused users to be redirected to the wrong organization.
orb list now has an optional flag, --json, that provides machine-readable output. In addition, the CLI command orb source has been updated to allow you to pull any version, including dev versions, for example:circleci orb source mynamespace/myorb@dev:foo
circleci orb source mynamespace/myorb@1.2.3
circleci orb source mynamespace/myorb@volatile
Cloud Performance plans have been updated to display multiple periods of usage data on the Settings page.
The CircleCI API documentation has been re-published with a completely new design and updated content, see the API Reference.
CircleCI 2.1 config keys are now available for reusing commands, executors, and parameters to simplify your .circleci/config.yml file. See the Reusing Config document for examples and instructions. Refer to the Configuring CircleCI reference for 2.1 syntax requirements.
We have released the Xcode 10 image on CircleCI 2.0. Add the following to your .circleci/config.yml file to select that version of Xcode in your jobs:
macos:
xcode: "10.0.0"
Note: A known issue, for which a fix is in-progress, prevents shipping iOS apps built on the Xcode 10 image to the App Store.
New projects are now created with 2.0 config by default and have Build Processing enabled.
CLI users are now prompted to switch to the updated CLI. All commands are backwards compatible, however some have been officially renamed. For example, the circleci build command is now an alias for the circleci local execute command.
For Performance Plans, total build minutes and credit usage for top projects is now displayed on the Plan Usage page. This can be found under Settings > Plan Usage
For Linux Plans, there is an improved path for adding containers on the Plan Overview page. This can be found under Settings > Plan Overview
Disabled Fixed notification through email or chat, if you have defined workflows as part of your configuration.
A Rerun workflow from beginning button is now on the Jobs page.
A 1.0 Project Badge for all projects still building on CircleCI 1.0 appears on Github.
Builds for new projects now require a CircleCI 2.0 config. 1.0 builds are no longer available for new projects. Builds for new projects without a 2.0 config will be blocked.
Updated error message when builds are not run if free minutes are depleted.
Updated information architecture with redesigned Welcome page and navigation menu for CircleCI Documentation is now available.
Auto-cancel of redundant builds now supports workflows. Customers will need to turn on the Build Processing option under Advanced Settings in their project settings. See the istructions for Enabling Auto-Cancel for Workflows Triggered by pushed to GItHub or the API for details.
A new version of the Local CLI is available. Customers using the existing Local CLI can update using the circleci-update command followed by the circleci switch command. Refer to Using the CircleCI Local CLI for the update instructions.
Performance customers can now see the billing period dates on the Plan Overview page.
A new Plan Overview page that shows the details for plan selection and a new Plan Usage page that shows usages for any applicable Linux and macOS plan.
build_parameters options that the job-triggering endpoint supports.The Workflows page of the CircleCI app now displays the username associated with rerunning a workflow, approving a job, or cancelling a job.
Performance improvements were made for workflows pages that reduce the load time for all workflows pages.
Custom Performance Plans now appear with active users for the month on the Plan Overview page.
Alerts for users who have depleted the free Linux build minutes for the month.
.circleci/config.yml file: macos:
xcode: "9.4.1"
Fixed a known issue with the CircleCI workflows UI due to . period character in the workflows name.
Fixed the interaction of the Workflows Rerun dropdown menu by restricting to open-source project users who are part of a GitHub organization.
CircleCI has developed an improved builds service that is ready for preview. The improved build service is the first step to a healthy roadmap of parameterized commands, config reuse across projects, improved DRY support, and better error reporting.
A preview is currently available for a few of our most adventurous organizations this week, and we plan on rolling it out to more projects in the coming weeks before it is publicly available. If you are adventurous and want to switch to the new service, be sure to read the preview docs before requesting approval.
With 2.0 you can do a lot more with the config.yml file. However, there are those times when edits result in schema errors. The CircleCI config processor now creates and returns a specialized Job that references the specific schema error(s) in the Job list. Learn more about our recent move to the terms Workflow and Job.
The following features and additions are now available.
New Workflows Feature: If your project has a large number of tests, you can use the circleci tests split command to reduce your job run time. This feature is now supported with Workflows. For more information on how to set up test splitting, see the Splitting Test Files section of the Running Tests in Parallel documentation.
EOL Tools: The 1.0 migration center has been updated with additional content and helpful tools.
Performance Improvement: CircleCI has upgraded the mechanism that returns gettimeofday calls. As a result, heavy users of syscall will see an aggregate improvement in performance. Most noticeably this will improve the run time of projects with heavy usage of profiling tools and Xdebug with PHP.
Added: This release adds a Plan Overview page for customers on the Performance pricing plan to enable Admins to see their selection from the Settings.
Added: Customers who are still building on CircleCI 1.0 will now get a reminder to upgrade to CircleCI 2.0 in build emails.
We have released the Xcode 9.3 image on CircleCI 2.0. Add the following to your .circleci/config.yml file to select that version of Xcode in your jobs:
macos:
xcode: "9.3.0"
It is now possible to create multiple Contexts in the Organization Settings of the CircleCI app. See the Contexts documentation for details and naming conventions.
We have released the Xcode 9.2 image on CircleCI 2.0. Add the following to your .circleci/config.yml file to select that version of Xcode in your jobs:
macos:
xcode: "9.2.0"
The release of CircleCI 2.0 for macOS enables your iOS projects to benefit from the significant performance, stability, and reliability improvements in the CircleCI 2.0 platform, including the following new features:
Workflows: Orchestrate jobs and steps with great flexibility using a simple set of new keys in your configuration. Increase the development speed through faster feedback, shorter reruns, and more efficient use of resources.
Advanced caching: Speed up builds by caching files from run to run using keys that are easy to control with granular caching options for cache save and restore points throughout your jobs. Cache any files from run to run using keys you can control.
Get started with the complete set of documentation for the macOS platform:
Docker Layer Caching is now available as a premium feature for the machine executor. Refer to the Docker layer Caching in Machine Executor section for instructions.
The button on the Jobs page has changed for jobs that run as part of a workflow. The rebuild options that are not compatible with Workflows have been removed from the button on the Jobs page. Jobs that ran as part of a workflow will only include the Rerun Job with SSH button on the Jobs page.
To rerun a job that ran as part of a workflow, you must navigate to the Workflows page of the CircleCI application and either rerun your entire Workflow or rerun your Workflow from failed jobs.
This feature enables Workflows to run on a configurable schedule. Refer to the Scheduling a Workflow section of the Orchestrating Workflows document for instructions and examples. Reference information for syntax is available in the triggers section of the Writing Jobs With Steps document and answers to common questions are documented in the Workflows section of the Migration FAQ.
Today we updated our Xcode 9.0 image with the just released Xcode 9.0 GM Seed (build version 9A235). Please check out this post on our Discuss site for more details on how to use the latest Xcode in your macOS builds.
This feature adds the used minutes to your Org Settings > Plan Settings page. This feature displays used minutes against Linux machines. It expands on our current functionality which shows minutes used against OS X machines and is located on the same page: Org Settings > Plan Settings.
Data appears for Orgs with a billing date after Aug 31, 2017. So, a new org will immediately see minutes used, and existing orgs will see the minutes used appear within the coming 30 days, depending on the billing date for your plan.
This feature enables an interactive graph of your workflow configuration. Refer to the instructions and examples in the Orchestrating Workflows document.
Today we updated our Xcode 9.0 beta 3 image to Xcode 9.0 beta 5 (build version 9M202q) with the latest simulators.
You can use this image by specifying Xcode 9.0 in your circle.yml:
machine:
xcode:
version: "9.0"
This image tag will be automatically upgraded when new betas are released by Apple, until the final release of Xcode 9.
This feature enables sharing of global environment variables across projects. Refer to the instructions and examples in the Setting Contexts document and the Job Contexts Example section of Orchestrating Workflows.
This feature enables filtering on Git tags for jobs in workflows using CircleCI 2.0. CircleCI will not run a job for a Git tag unless a tags filter is specified. Refer to the instructions and examples in the Workflow Tags section of Writing Jobs With Steps and in the Git Tag Job Execution section of Orchestrating Workflows.
CircleCI 2.0 is a completely updated CI/CD platform that starts every run with a clean image which is automatically provisioned just-in-time for Linux and Android jobs on the hosted CircleCI application.
Configuration moves into the code in 2.0, so every developer can configure jobs directly in their working branch, teams can try new things without the risk of slowing anyone else down, and business leaders have the ability to operate large global teams with minimal overhead. CircleCI 2.0 prevents you from writing clean-up scripts because every run starts in the same state, eliminating the risk of polluting a test database or leaving files in places that cause problems for the next run.
The CircleCI 2.0 platform includes significant performance, stability, and reliability improvements along with the following new features:
First-class Docker Support: Choose any image to run your job steps, customizable on a per-job basis on a particular Git branch. Speed up your run times with advanced layer caching. Build docker images with full docker CLI support and full support for docker compose. Support for all programming languages and custom environments that offer more predictable output. See Specifying Container Images for instructions.
Workflows: Orchestrate jobs and steps with great flexibility using a simple set of new keys in your configuration. Share temporary files between jobs with workspaces for fan-in, fan-out, parallel, and sequential runs. Hold a workflow for a manual approval and restart a workflow from a failed job. See Orchestrating Workflows for details.
Resource Allocation: Configure your CPU and RAM needs on a per-job basis at the branch level, see the resource_class documentation for instructions. Paid accounts may request this feature from their Customer Success Manager, non-paid users may request to get started by sending email to support@circleci.com.
Insights: Access interactive charts and analyses in seconds. Visualize trends in your build history to identify and pinpoint bottlenecks. Understand all of your builds at a glance. View the builds that fail most, so you can fix the slowest tests to improve efficiency. See the Collecting Test Metadata documentation for information.
Debugging with SSH and CLI: Perform local job runs, configuration validation and SSH in to builds for access to log files and debugging running processes. See Using the CLI documentation to learn about running local jobs and refer to Debugging Jobs over SSH for SSH instructions.
Parallelism: Automatic provisioning of containers as they are freed without waiting for other jobs to finish. See the Parallel Job Execution documentation for examples.
Advanced Caching: Speed up builds by caching files from run to run using keys that are easy to control with granular caching options for cache save and restore points throughout your jobs. Cache any files from run to run using keys you can control, see the Caching Dependencies documentation for strategies and steps.
Demonstration Applications: See the Language Guides and Demo Repos to learn CircleCI configuration by example for applications written in Go, Javascript, PHP, Python (Django and Flask), Ruby on Rails, Java, Elixir, and Clojure.
New Documentation: New and restructured documentation including an Overview, Hello World, Sample 2.0 config.yml File, simplified instructions for Migrating from 1.0 to 2.0, plus examples for Configuring Databases and Creating Custom Docker Images. Refer to the Migration FAQ for common questions and known limitations.
A fix to the pricing plan has been implemented which limits Linux plan capacity to the published maximum. As a result of this change, you may see builds queuing until the requisite containers are available.
This feature enables core dumps for projects using CircleCI 2.0. Get core dump files and push them as artifacts for inspection and debugging using the instructions in the Uploading Build Artifacts document.
Today we updated our Xcode 9.0 beta image to Xcode 9.0 beta 2 with the latest 10.2 simulators. To start using it, add the following to your circle.yml:
xcode:
version: "9.0"
This image tag will be upgraded automatically when new betas are released by Apple, until the final release of Xcode 9.
For mobile, we have just released a build image that allows you to use the latest stable version of Xcode, 8.3.3. To start using it, add the following to your circle.yml:
xcode:
version: "8.3.3"
The Workflows feature is available on CircleCI 2.0. It is designed with a flexible algorithm to support very complex job scheduling and orchestration using a simple set of new configuration keys. See the Steps to Configure Workflows section of the Migrating from 1.0 to 2.0 document for instructions. Refer to the Orchestrating Workflows document for examples and conceptual information.
This update makes Xcode 9 Beta available for all macOS builds. Specify version 9.0 in your circle.yml file to override the default.
This feature enables users to log in to CircleCI with a Google account and provides new users with the opportunity to experience the application and selected demo projects without providing access to their code repository.
Now you can filter your build emails by project without doing subject matching. This feature adds the standard List-ID header with organisation.project.notifications.circleci.com to make it easy to filter build emails into per-repo or per-org folders.
This feature enables you to import project environment variables from projects in the same organization to save time and typing. On the Settings screen for your project, click the Import Variable(s) button on the Environment Variables page and select from the list.
This feature enables you to join CircleCI without providing access to your private GitHub repos. To limit access, select Public Repos Only from the Start with Github menu on the signup page.
Looking for the builds most relevant to your actions? You can now filter builds by “my builds” (builds you triggered) or “all builds” (builds triggered by other users on your team). The filter can be found near the top, right-hand corner of your dashboard. Currently, this feature is only available on the organization and project-level.
The logs produced by the Fastlane tools are now being stored as build artifacts so that you can easily access them later.
It is now possible to control whether to run builds for pull requests coming from forks and whether to pass the secrets from the main project to the fork on such builds, via two separate settings. Check out the Advanced Settings tab for your project for more details.
A few weeks ago we started downloading CocoaPods specs from S3 instead of Git in projects that use our iOS inference. It is now also possible to download the specs from S3 in projects with manual configuration.
Please check out this Discuss post for an example of downloading specs from S3 via a circle.yml command.
It is now possible to upload provisioning profiles under the ‘Permissions’ section of your OS X project settings. Once uploaded, we will automatically import the profiles during your OS X builds. Profiles are encrypted at rest on the CircleCI side.
This update removes the need to keep the provisioning profiles checked into your repository and simplifies the setup of code signing for new OS X projects.
CircleCI offers the ability to link directly to build output steps. We’ve now extended this feature into build email notifications. You should now see a clickable ‘Failing Command’ on (failed) build notification emails which will open the build page to the failed command in your build output.
We have added a confirmation message to prevent users from accidentally stopping the builds on CircleCI.
We have added functionality to click through the ‘Build Timing’ graph to access different sections of the build.
Users can show share link to a particular step within their build output; Eg. https://circleci.com/gh/spotify/helios/5091#tests/containers/0/actions/4
We have added flash notification when users add or remove Apple Code Signing key, API permissions, SSH key or environment variables.
The Xcode 13 RC image is now available on CircleCI macOS resource classes. This image replaces Xcode 13 Beta 5. For further details, please see the Image Manifest.
Note: This image contains potentially breaking changes for NodeJS and Ruby 2.5 users upgrading from Xcode 12 images. For more information about these potential changes, refer to the following Discuss post.
This update includes updated executor images for Go version 1.17 and Node.JS 14.17.5. CircleCI updates Windows images monthly, which includes Microsoft’s latest patches, as well as renewing Visual Studio 30-day licenses.
We have updated the Plan Overview page, so organizations on our free plans can now learn more about the Performance Plan, see details on pricing / estimates and see our top features on CircleCI.
Webhooks are now available to all users. A webhook enables you to connect a platform you manage (either an API you create yourself, or a third party service) to a stream of future events.
Setting up a Webhook on CircleCI enables you to receive information (referred to as events) from CircleCI, as they happen. This can help you avoid polling the API or manually checking the CircleCI web application for desired information.
For more detailed information about webhooks, please see the Webhooks documentation, which can be found here.
Several new features have been released to improve the user experience when setting up configurations.
Configuration sandbox
We have shipped a configuration sandbox so you can get immediate feedback while building your configuration. In this new experience, you can see the effect of your configuration change in a sandbox environment and offer corrections in the context of CircleCI configuration to get up and running faster.
Guide me - with orbs
We know users enjoy using orbs, therefore, we have made it easier to use and build a configuration with orbs. For new users, you will be able to walk through a series of steps that will take you through constructing a configuration using orbs.
Project setup for users w/existing configurations
We have made it easier for users who are ready to go and just want to build their projects on CircleCI. With this update, users now have the option to directly commit from any branch.
There have been a number of feature and user experience updates made to the CircleCI platform, which are described below.
Blue dot on artifacts and updated empty state
We have made it easier for you to recognize when you do not have artifacts already set up. With this update, you will now see a blue “unread” dot displayed on the Job Page Artifact tab, as well as some example use cases, such as storing HTML reports or screenshots, to help you get up and running faster.
Status badge generator in project settings
Status badges are now available in Project Settings. This feature enables users to create a status badge more quickly for showing statuses on GitHub.
Add parameters to manual pipeline run
Users can now add one or more parameters when running a pipeline manually from the UI.
Iteration on copy step line link
We’ve made it easier for you to copy your code! When you hover over any part of a line in the step output, you’ll be able to see a blue copy icon.
Follow project from branch drop down
If you happen to not have a project selected on CircleCI previously, you might have not been able to navigate to the page you’re looking for. Now when you select the drop-down, you can directly follow projects directly from the branch drop down and ensure you get to the project and page data you’re looking for.
Workflow status filter
Users may now filter to any combination of specific workflow statuses. Note that you may need to click the “See more” button if there are additional results.
You should receive an automated response notifying you that we received your info. Someone from our Enterprise team will be reaching out to you shortly.
You should receive an automated response notifying you that we received your info. Someone from our Enterprise team will be reaching out to you shortly.