| commit | 2c3d596477f79347d980b4943fac405358170de8 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Wed Sep 22 16:52:48 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 22 16:52:48 2021 +0000 |
| tree | 3ba79c7ffb4b26edae54c276c239892cae629729 | |
| parent | a2866c6f4c076f3fa9683937e79e80e28f20b1a3 [diff] |
Use main when checking out cocoon repository. This is part of the migration of the master branch to main. Before making main the default branch. Change-Id: I6d66587faec85829e1181ff1ce6f9e2a49a07dbb Bug: https://github.com/flutter/flutter/issues/90476 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/18361 Reviewed-by: Casey Hillers <chillers@google.com> Commit-Queue: Godofredo Contreras <godofredoc@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Actual builds can be seen at ci.chromium.org.
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.
Tricium configurations recipes repo.
The script branch_recipes.py is used to generate new copies of the LUCI recipes for a beta release. See Recipe Branching for Releases for more information. For usage:
$ ./branch_recipes.py --help