-
Notifications
You must be signed in to change notification settings - Fork 29.1k
Open
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projectteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team
Description
Flutter infra team has been spending quarters effort to scale running tasks. One big milestone is separating tasks to subbuilds to improve efficiency and enhance reusability.
- Engine targets are now being migrated to engine_v2, which separates different logics into their own self-contained steps: build, test, generator, archive. flutter.dev/go/engine-build-definition-language
- Framework devicelab targets are now being migrated to build+test models go/devicelab-build-test
The current scheduling workflow however is bearing with several issues:
- it needs an orchestrator build to schedule all subbuilds
- any single subbuild fails will cause the whole orchestrator build failure
- the latter subbuild can only be triggered after all artifacts are finished building, though may need only one of them
This bug tracks a smart graph scheduling logic for these dependent targets to save resources and validation time.
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projectteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team