| commit | 7a21186796e7e164dd2179d992dca8fa592adc97 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Wed Apr 24 20:54:45 2024 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 24 20:54:45 2024 +0000 |
| tree | 2874f8c6ae98840ce5e6b647d713eeaf4218d7b5 | |
| parent | 63b1ba0f9cf3ba76f67804af21d7c76df8f233ac [diff] |
Implement the execution of flutter shard tests in engine prs. This CL is adding the following functionality: * prod builds using the experimental realm will now upload the artifacts to a non production gcs bucket. * try builds will be uploading artifacts to a namespaced path using the buildbucket id. * Minimum changes to tester.py recipe to implement the paths expected for non monorepo builds. * Changes to shard util to always pass the parent commit and buildbucket id as properties of subbuilds. Bug: https://github.com/flutter/flutter/issues/146599 Change-Id: Ib92383ace36034dc8b2c217c861d77b99ed08adf Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/57140 Reviewed-by: William Hesse <whesse@google.com> Reviewed-by: Ricardo Amador <ricardoamador@google.com> Commit-Queue: Godofredo Contreras <godofredoc@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.
Supported repositories roll their .ci.yaml into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.
Please follow instructions on Contributing docs to set up your development environment.