Skip to content

Conditionally skip the engine build phase #162201

@matanlurey

Description

@matanlurey

We'll use the same logic we use for runIf to determine if the engine sources changed::

  • DEPS
  • engine/**

If there are >= 30 files or one of the files above changed, we keep doing what we do now (i.e. build the engine before scheduling engine and framework tests).

Otherwise, in this new flow (TM):

This, combined with the work we already did/are doing, see #162118, means that we'll fetch and use an older engine artifact.


There is future work to do to expand beyond the 30 file limit (see #161462), but we believe this would address many framework-only PRs today, allowing us to fix the limitations we have today of understanding what files changed (and eventually move towards something like a precomputed build plan).

Metadata

Metadata

Labels

P1High-priority issues at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: tech-debtTechnical debt, code quality, testing, etc.fyi-frameworkFor the attention of Framework teamteam-infraOwned by Infrastructure team

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions