Change engine checkout to gclient unmanaged mode

Gclient managed mode has been deprecated for many years.
It does not make much difference in automated builds, but
it does make gclient sync revert local changes in the main
solution repository containing DEPS.

This use of [config].solutions.add() to create a gclient solution
is the only instance in recipes or recipe_modules of a explicitly
constructed solution.

The solutions created by the depot_tools fetch flutter command
already have managed: False.

Change-Id: I83fc086a79a1a63dd40761b1efe8237a80480e2b
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/26640
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Commit-Queue: William Hesse <whesse@google.com>
316 files changed
tree: 95985cb8d1225c0150a668d370ebb261c1cc6774
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. branch_recipes.py
  8. LICENSE
  9. OWNERS
  10. README.md
  11. recipes.py
README.md

Flutter LUCI Recipes

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.

Configuration

Tricium configurations recipes repo.

Recipe Branching for Releases

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