Currently a builder group is defined by defining a console. Change that:
- add top-level repeated "group" field which defines a list of builders
- add "console_id" field to the group message. It references another console in the same project by the id
- remove header_id from console proto. There is no need to define a header separately now that console is reused in different groups.
- update infra and chromium configs. The number of console entries should be ~= number of different repos.
Currently a builder group is defined by defining a console. Change that:
- add top-level repeated "group" field which defines a list of builders
- add "console_id" field to the group message. It references another console in the same project by the id
- remove header_id from console proto. There is no need to define a header separately now that console is reused in different groups.
- update infra and chromium configs. The number of console entries should be ~= number of different repos
- add BuilderGroup entity, update it from configs and use it places where common.Console is used as a group
Comment 1 by efoo@chromium.org
, Nov 28 2017