elastic / integrations

Elastic Integrations
https://www.elastic.co/integrations
Other
30 stars 447 forks source link

[ci] Add team labels to failing test issues #10354

Open andrewkroh opened 4 months ago

andrewkroh commented 4 months ago

We now have automation to create GH issues (example) when a package fails CI testing. Those issues include a mention of the GH team that owns the package (derived from codeowners). It would also be useful to label the issue with the associated "Team:" label because some team's have Github board automations that are driven by the labels.

So I propose we add a file in the same directory as CODEOWNERS that contains mappings from GH team names to labels. This mapping can be consulted by tooling (https://github.com/elastic/integrations/pull/10234) such that issues are labeled at creation time.

andrewkroh commented 4 months ago

Of the Github teams that are codeowners, these are the associated labels:

github_team github_label
elastic/cloud-security-posture Team:Cloud Security
elastic/ecosystem Team:Ecosystem
elastic/elastic-agent-data-plane Team:Elastic-Agent-Data-Plane
elastic/fleet Team:Fleet
elastic/obs-cloudnative-monitoring Team:Cloudnative-Monitoring
elastic/obs-ds-hosted-services Team:obs-ds-hosted-services
elastic/obs-infraobs-integrations Team:Obs-InfraObs
elastic/obs-ux-infra_services-team Team:obs-ux-infra_services
elastic/search-extract-and-transform Team:Search-Extract and Transform
elastic/sec-applied-ml Team:Security-Applied ML
elastic/sec-deployment-and-devices Team:Security-Deployment and Devices
elastic/sec-linux-platform Team:Security-Linux Platform
elastic/sec-windows-platform Team:Security-Windows Platform
elastic/security-asset-management Team:Asset Mgt
elastic/security-service-integrations Team:Security-Service Integrations
elastic/stack-monitoring Team:Stack Monitoring