flutter/engine
Matan Lurey 74ab593738
Expand the .ci.yaml and builder.json linter (#161991)
Closes https://github.com/flutter/flutter/issues/161823.

Other than the integration test included, example output looks like
this:

```dart
# Assuming you are in $ENGINE/src/flutter
% dart tools/pkg/engine_build_configs/bin/check.dart --help
-v, --verbose                                  Enable noisier diagnostic output
-h, --help                                     Output usage information.
    --engine-src-path=</path/to/engine/src>    (defaults to "/Users/matanl/Developer/flutter/engine/src")

% dart tools/pkg/engine_build_configs/bin/check.dart       
 Loaded build configs under ci/builders
 .ci.yaml at .ci.yaml is valid
 All configuration files are valid
 All builds within a builder are uniquely named
 All build names must have a conforming prefix
 All builder files conform to release_build standards
```

I allow-listed a single case that needs to be moved, but I think this
provides value already.
2025-01-22 18:41:02 +00:00
..
scripts gclient template file clarifications (#160882) 2024-12-27 19:36:20 +00:00
src Expand the .ci.yaml and builder.json linter (#161991) 2025-01-22 18:41:02 +00:00
README.md Clarify where gclient is run from. (#160889) 2024-12-27 21:37:24 +00:00

Flutter Engine

gclient bootstrap

Flutter engine uses gclient to manage dependencies.

If you've already cloned the flutter repository:

  1. Copy one of the engine/scripts/*.gclient to the root folder as .gclient:
    1. Googlers: copy rbe.gclient to enable faster builds with RBE
    2. Everyone else: copy standard.gclient
  2. run gclient sync from the root folder