Repository navigation
The ci yaml roller should rebase to TOT when rolling config changes #112127
Description
Current state: ci.yaml roller rolls whatever is in the current commit.
Problem: earlier rolled ci yaml configs will be rolled back if the later landed commit doesn't rebase to TOT. This will cause latency of config changes, and cause confusion as well. The real change could be rolled back and forth depending on the commits' statuses.
Possible solution: rebase the commit to TOT in the ci yaml roller builder whenever a roller is happening.
Context: #112117
Activity
CaseyHillers commentedon Aug 25, 2023
I sent https://flutter-review.googlesource.com/c/recipes/+/50200 to fix the roller to pick up HEAD instead of roll at a specific SHA.
github-actions commentedon Sep 8, 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.