| commit | db2b43a4b8739c850bc5810f74958614f5d3568f | [log] [tgz] |
|---|---|---|
| author | Matan Lurey <matanlurey@users.noreply.github.com> | Thu Apr 17 17:51:39 2025 -0700 |
| committer | GitHub <noreply@github.com> | Fri Apr 18 00:51:39 2025 +0000 |
| tree | 9bd1b0cf408a33fc8d7f9fc3b35829d6fb6efd37 | |
| parent | 15f96c04343ad8586afea0c745638f2384b5576a [diff] |
Disable passing `FPEV=...` for release candidates for now. (#4541) At the moment, the ability to re-run prod tasks does not work (work gated on finishing the Firestore migration), and as such, we need the ability for `engine.version` files to work in post-submit so that there is a reliable way to test, otherwise it is not reasonably feasible (without hacking on the backend). See https://flutter-dashboard.appspot.com/#/build?repo=flutter&branch=flutter-3.32-candidate.0.  Filed https://github.com/flutter/flutter/issues/167383 to track re-enabling this. /cc @reidbaker
Cocoon is a Dart App Engine custom runtime (backend) with a frontend of Flutter apps (build and repository dashboard). Cocoon coordinates and aggregates the results of flutter/flutter builds.
It is not designed to help developers build Flutter apps.
Cocoon is not a Google product.
The server is driven by commits made to https://github.com/flutter/flutter repo. It periodically syncs new commits. If you need to manually force a refresh, query https://flutter-dashboard.appspot.com/api/refresh-github-commits.
You will need to be authenticated with Cocoon to do this.
Cocoon has several components:
A server, which coordinates everything. This is a Dart App Engine application. If you have never used that before, you may want to peruse the samples for Dart App Engine. The server is found in app_dart.
A Flutter app (generally used as a Web app) for the build dashboards. The dashboard is found in dashboard.
Cocoon creates a checklist for each Flutter commit. A checklist is made of multiple tasks. Tasks are performed by LUCI bots.
First, set up a Flutter development environment. This will, as a side-effect, provide you with a Dart SDK. Your life will be easier if you add that (.../flutter/bin/cache/dart-sdk/bin/) to your path.
To update the production server, you will need the Google Cloud SDK. Since there is no Dart SDK, we just use the command line tools.
All the commands in this section assume that you are in the app_dart/ directory.
dart bin/local_server.dart
This will output Serving requests at 0.0.0.0:8080 indicating the server is working.
New requests will be logged to the console.
To run live tests, build the app, and provide instructions for deploying to Google App Engine, run this command:
dart dev/deploy.dart --project {PROJECT} --version {VERSION}
You can test the new version by accessing {VERSION}-dot-flutter-dashboard.appspot.com in your browser. If the result is satisfactory, the new version can be activated by using the Cloud Console UI: https://console.cloud.google.com/appengine/versions?project=flutter-dashboard&serviceId=default
--profile: Deploy a profile mode of dashboard application for debugging purposes.
--ignore-version-check: Ignore the version of Flutter on path (expects to be relatively recent)
The dashboard application will use dummy data when it is not connected to the server, so it can be developed locally without a dev server.
To run the dashboard locally, go into the dashboard directory and run flutter run -d chrome. The dashboard will be served from localhost (the exact address will be given on the console); copy the URL into your browser to view the application. (The dashboard should also be able to run on non-Web platforms, but since the Web is our main target that is the one that should generally be used for development.)
You can run flutter packages upgrade to update the dependencies. This may be necessary if you see a failure in the dependencies.