| commit | fa625aedcfce59f89087f01d6bc8418f5f52640c | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Tue Feb 08 04:52:15 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 08 04:52:15 2022 +0000 |
| tree | 18569fbf6beb29b73918523e790079ab7ff41a47 | |
| parent | 65cfb8a4b87499ddba021143264d666fc67541a8 [diff] |
Duplicate engine and packaging recipes. This is in preparation to move organize the recipes in folders aligned with the repository where they are being used. We need to do this in three steps to avoid breaking the devlopement workflows: 1.- Duplicate the recipes in the target location 2.- Change .ci.yaml to point to recipes in the new location. 3.- Delete recipes from the source location Bug: https://github.com/flutter/flutter/issues/97735 Change-Id: Ieb60c6b83848b284eb6077dc793ae0600e06f702 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/26380 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