| commit | b57a9e4e77a11af38a7facfdefa53f1e73f34a66 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Thu Jan 27 00:35:43 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 27 00:35:43 2022 +0000 |
| tree | 0523d64e17aba3de52c844339c931069628d3220 | |
| parent | 144dcaf4e5d7053151bf76da43f129f4f86159ea [diff] |
Ensure master is checked out on customer tests. The customer tests require both the branch under test and master to be checked out to identify the commit point from flutter/tests to use. Bug: https://github.com/flutter/flutter/issues/97272 Change-Id: I2af6c5cccf224d546f34bd94ce7767eaf4a4e9ab Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/25820 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