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

Clone this repo:


  1. 654c5c6 [dart_ci] Add a script to schedule builders for script executables by Karl Klose · 6 weeks ago master
  2. ebb5c56 Fix bucket location for artifacts downloaded by symbolizer. by Vyacheslav Egorov · 9 weeks ago
  3. 60b4a03 Tweak the format of the notification email. by Devon Carew · 9 weeks ago
  4. 75a887b [appengine] Fix a bug in computing the base name by Karl Klose · 9 weeks ago
  5. 5dab3d3 [appengine] Update overview page's title and unify placeholders by Karl Klose · 9 weeks 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.