Skip to content

Access luci build configuration files from separate repositories #62429

Closed

Description

@keyonghan

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

Activity

  1. self-assigned this
    on Jul 28, 2020
  2. changed the title [-]Move luci build configuration files to separate repositories[/-] [+]Access luci build configuration files from separate repositories[/+] on Aug 6, 2020
  3. keyonghan commented on Aug 11, 2020

    @keyonghan
    ContributorAuthor

    All tasks related to this issue have been implemented. Waiting cocoon to pick them up and validate their effectiveness.

  4. keyonghan commented on Aug 11, 2020

    @keyonghan
    ContributorAuthor

    works as expected. Closing.

  5. github-actions commented on Aug 17, 2021

    @github-actions

    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.

  6. locked as resolved and limited conversation to collaborators on Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listteam-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions