Skip to content

Separate tests from builds that generate artifacts #145842

@matanlurey

Description

@matanlurey

From @godofredoc on an internal doc on "Engine Goldens + Cherrypick Workflow":

Would it be possible to add a goal to separate tests from the builds generating artifacts?

The context of this request is that builds that generate release artifacts run on secure infrastructure that can only be triggered by new commits and manual runs with multiparty approvals. This would mean that if goldens get blocked on small differences that are manually approved the entire release process can be delayed. If all the tests are separated to its own builders then we would be able to retry from the dashboard without MPAs and huge delays because of the limited resources.

Happy to provide more details if needed.

As of right now, (I believe) @godofredoc is suggesting this should be a blocker to having a cherrypick workflow on the release branch, and I tend to agree with him that without this separation we'd be putting a lot of burden on release engineers.

Anyway, filed as an issue to discuss with the engine/web team. Feel free to chime in.

/cc @zanderso @gaaclarke @jonahwilliams @mdebbar for a start.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: proposalA detailed proposal for a change to Flutterc: tech-debtTechnical debt, code quality, testing, etc.team-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions