flutter/packages builds are not hermetic

flutter/packages .cirrus config fetches directly from latest master and uses pub global activate to install flutter_plugin_tools. A build that succeeds at one point in time can fail next time at the same commit simply by fetching a different version of Flutter or plugin tools (example build breakage).

Culprit: https://github.com/flutter/packages/blob/85135ddad047d82aa5025496410a41b031c4c5df/.cirrus.yml#L7-L11

Should we start by defining owners of the repo?

I recently changed the tools version to be pinned, so that's resolved. For Flutter, using the latest master/stable is generally a feature, so I wouldn't want to change that without having an autoroller constantly moving the version forward (which would certainly be better).

master switched to an autoroller a while ago, so the only piece left here is the unpinned stable, which will be fixed by flutter/packages#2328

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

Navigation Menu

Repository navigation

flutter/packages builds are not hermetic #68934

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

flutter/packages builds are not hermetic #68934

Description

Activity

godofredoc commented on Oct 29, 2020

stuartmorgan-g commented on May 15, 2021

stuartmorgan-g commented on Jul 18, 2022

github-actions commented on Aug 2, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions