| commit | b35046f33f5dbf9490dd51a584da1c91d83a7ee0 | [log] [tgz] |
|---|---|---|
| author | Josip Sokcevic <sokcevic@google.com> | Sat Aug 21 00:32:13 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Aug 21 00:32:13 2021 +0000 |
| tree | 0c1466b38d449d59a5de6d4c458b798ac6864864 | |
| parent | 751d63c7eed434bf4bf0ab8a546f41c90bc5bb69 [diff] |
Explictly set branch in bot_update & git checkout depot_tools recipe made a change so the expected default branch is main. This sets branch to flutter's current default. Bug: chromium/1241955 Change-Id: I96bc6f3ce96e417d1e051dfbba108cdecf8fac77 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/17281 Commit-Queue: Casey Hillers <chillers@google.com> Reviewed-by: Casey Hillers <chillers@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