Issue metadata
Sign in to add a comment
|
[Component Request] New Infra>Platform>Swarming>Customers |
||||||||||||||||||||||
Issue description1] Component Name: Customers 2] Parent Component: Infra>Platform>Swarming 3] Description of Component: Problems related to Swarming usage, e.g. configuration, capacity 4] Admin/ Owner: maruel 5] Please specify what triage practices will be followed for the component Please make me auto-cc
,
May 5 2018
It's for bugs related for Swarming customers in the sense that it's an issue in the way they are *using* the server, not a problem with the server or the bot implementation. Perf wants a new bot or change ACL, another team wants bot_config customization, enabling monitoring on a specific instance, etc. In theory it should be a label, but I know that in practice it wouldn't work as people think of Swarming as a service (it is in fact) and really want to file their bug there. Example of bugs I'd put in this component: https://crbug.com/839022 https://crbug.com/837197 (the bug itself, not follow ups) https://crbug.com/833888 https://crbug.com/832766 https://crbug.com/831707 https://crbug.com/831612 That said I'm open to suggestions but I really want these bugs to go away, but they may not have other relevant component to put them into.
,
May 15 2018
s/Customer/Admin/? If so, sgtm.
,
May 15 2018
Ok
,
Jun 5 2018
Ping?
,
Jun 15 2018
This delay was unacceptable, my apologies. Done. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by efoo@chromium.org
, May 4 2018Owner: efoo@chromium.org
Status: Assigned (was: Untriaged)