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
Access luci build configuration files from separate repositories #62429
Existing Luci builder configurations are stored in cocoon project. This is not efficient because we need to re-deploy the flutter-dashboard after changing the builder configuration. Additionally, with different channels/branches, a single place becomes challenging to support various requests.
Moving corresponding build configuration files to different repositories will make things easier. Repos/branches will maintain their own copy of builder config file. From cocoon side, it can directly obtain the build config file for different repos/branches without redeploying the app engine.
add configs to flutter
add configs to engine
add configs to packages
add configs to cocoon
add logic to access configs from separate repos
update APIs to use newly added logic
remove old existing logic which returns all builders across all repos
changed the title [-]Move luci build configuration files to separate repositories[/-][+]Access luci build configuration files from separate repositories[/+]on Aug 6, 2020
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
[-]Move luci build configuration files to separate repositories[/-][+]Access luci build configuration files from separate repositories[/+]keyonghan commentedon Aug 11, 2020
All tasks related to this issue have been implemented. Waiting cocoon to pick them up and validate their effectiveness.
keyonghan commentedon Aug 11, 2020
works as expected. Closing.
github-actions commentedon Aug 17, 2021
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.