github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify how/when FLUTTER_PREBUILT_ENGINE_VERSION is passed in Flutter's CI (#167204)

Browse Source 
See also: https://github.com/flutter/website/pull/11903.
This commit is contained in:
Matan Lurey 2025-04-15 11:07:04 -07:00 committed by GitHub
parent 3595e7dad0
commit 38eaface2f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/tool/Engine-artifacts.md
View File

@ -1,5 +1,7 @@
# How `flutter` fetches engine artifacts
[flutter.dev/to/engine-artifacts](https://flutter.dev/to/engine-artifacts)
While in the same repository, the `flutter` (tool), which is used to run and
test the framework, needs to know how to download the engine artifacts for the
current platform and target device. Engine artifacts include `dart` (the
@ -49,6 +51,22 @@ stateDiagram-v2
UseMergeBase --> [*]: Done
```
## Flutter CI/CD Testing
On Cocoon (Flutter's internal CI/CD) we _often_ set
`FLUTTER_PREBUILT_ENGINE_VERSION` to the following:
| Branch | Presubmit | Merge Queue | Postsubmit |
| ------------------------- | ------------ | ------------------ | ------------------ |
| `main` | `commit.sha` | _Uses normal flow_ | _Uses normal flow_ |
| `flutter-x.x-candidate.x` | `commit.sha` | N/A[^1] | `commit.sha` |
> NOTE: `engine.version` is intentionally ignored in release candidate
> post-submit builds. See
> [#167010](https://github.com/flutter/flutter/issues/167010).
[^1]: Release candidates do not use a merge queue.
## References
The script(s) that compute (and test the computation of) the engine version: