You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use generic flutter/infra builders for release infrastructure #97265
Even though the release branches have their own copy of the .ci.yaml if a builder configuration is renamed/removed it impacts release branches presubmit because the builds enumerated in the release branch .ci.yaml file does not exist anymore.
Once #95037 is implemented, we can move this to a bootstrap builder in LUCI. That would allow for the targets to run in presubmit for release branches.
changed the title [-]Renaming/removing build configurations impact release branches[/-][+]Use generic flutter/infra builders for release infrastructure[/+]on May 5, 2022
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.
Activity
godofredoc commentedon Jan 26, 2022
\cc @itsjustkevin @CaseyHillers
CaseyHillers commentedon Jan 26, 2022
Once #95037 is implemented, we can move this to a bootstrap builder in LUCI. That would allow for the targets to run in presubmit for release branches.
[-]Renaming/removing build configurations impact release branches[/-][+]Use generic flutter/infra builders for release infrastructure[/+]CaseyHillers commentedon Jun 8, 2022
I met with Fuchsia and Pigweed, and I'm going to experiment with building a Dart implemented luciexe to achieve this
CaseyHillers commentedon Aug 4, 2022
I created CaseyHillers/cocoon@aad6569 to port the initial models over. LUCI hasn't enabled the RPC yet for Cocoon to use, so this is still blocked.
godofredoc commentedon Dec 7, 2022
Obsolete with the migration to dart-internal.
github-actions commentedon Mar 4, 2023
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 -vand a minimal reproduction of the issue.