Mapping component_id -> Monorail Component

[Andrew Grieve]

The SuperSize tool still looks for "monorail.component" within DIR_METADATA files. However, many new directories are being created with only buganizer.component_id, and no monorail.component.

Is there a file or command that can be used (locally and by trybots) that can get the textual component name given a buganizer id?

[Takuto Ikuta]

I don't know if there are such tools, but I found one public script which may use the buganizer API.

https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/tools/blinkpy/w3c/buganizer.py

But asking this kind of question in the internal mailing list may give you a better answer.

On Tue, Jun 4, 2024 at 4:59 AM Andrew Grieve <agr...@chromium.org> wrote:

The SuperSize tool still looks for "monorail.component" within DIR_METADATA files. However, many new directories are being created with only buganizer.component_id, and no monorail.component.

Is there a file or command that can be used (locally and by trybots) that can get the textual component name given a buganizer id?

--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CABiQX1V0StUVCpNQz%2BobeVHa7Uh6jkNHKZQSn3D8KmzUxqUUEQ%40mail.gmail.com.