Clean up Frontend task stages #3685
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has been a technical debt to support Task
stagesin both dashboard and backend: we used to supportcirrus,travis,chrome,google,LUCI,cocoonas stages. Over past years, we have been refactoring everything in LUCI, and there is no need to maintain stages.Now the only
stagetasks we support isdart-internalones, which are still LUCI though. To distinguish these tests, we reuse the concept ofstage, but this PR simplifies corresponding logics.This PR prepares for Frontend switch over to Firestore, which doesn't support
stageany more.Part of flutter/flutter#142951