Remove is_fusion conditions for recipes/infra/ci_yaml.

Removes at best unused code, and at worst, blindspots for bugs as many
of our tests across flutter/recipes exclusively refer to the engine repo, even though it no longer exists.

This CL uses "repo == 'flutter'" to conditionally add the engine .ci.yaml.

Change-Id: Iff23f599e5ea79b611652969297d63b3951d8dfa
Bug: https://github.com/flutter/flutter/issues/170843
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66743
Commit-Queue: Matan Lurey <matanl@google.com>
Reviewed-by: Jason Simmons <jsimmons@google.com>
Reviewed-by: John McDole <codefu@google.com>
6 files changed
tree: 39f7033eb202758d20f61b7a96002a7a8481fbdb
  1. .vscode/
  2. infra/
  3. recipe_modules/
  4. recipes/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. CONTRIBUTING.md
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.

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.

Contributing

Please follow instructions on Contributing docs to set up your development environment.