Tools used by Dart's continuous integration (CI) testing that aren't needed by Dart SDK contributors

Clone this repo:


  1. 5bea28c [baseline] Upload per-configuration results by Alexander Thomas · 4 weeks ago main master
  2. 18e70b6 [results feed] Avoid exception when a CL patchset number is too high by William Hesse · 9 weeks ago
  3. 77c8c70 [appengine] Migrate to null safety by Alexander Thomas · 2 months ago
  4. 6507265 [current results] Migrate current results server to official Docker image by William Hesse · 2 months ago
  5. d71ddcd [current results] Migrate the current results server to null safety by William Hesse · 2 months ago


Tools used by Dart's continuous integration (CI) testing infrastructure.

The repository is based at It is mirrored to Do not land pull requests on Github.

Results Feed

The results feed is an angular Dart application that displays changed results from the CI and from CQ runs (tryjobs). The code is in the results_feed directory. It is deployed to, using Firebase hosting.

Cloud functions

The automated testing of Dart on the CI and CQ publishes results to Cloud Pubsub, and cloud functions triggered by those Pubsub messages process the data and store it in Firestore. These functions are located in the functions directory, and are deployed on the dart-ci Google Cloud project.

Github Label Notifier

Internal users get automatic notifications of new GitHub issues created in certain repositories, by subscribing to issue labels on those repositories. This tool provides a UI for internal users to subscribe to their chosen issue labels. That UI is hosted at It also defines cloud functions that are triggered by GitHub webhooks and use the issue label subscriptions to send email notifications using SendGrid.