-
Notifications
You must be signed in to change notification settings - Fork 108
Open
Description
An issue surfaces recently when we try to onboard repo from meta-pytorch onto HUD https://fburl.com/workplace/j063m9ot. This usually is a 2-step processes:
- Onboard the repo to PyTorch bot app
- Add
github-status-testwebhook to receive all the events (although we only processworkflow_jobandworkflow_runhttps://github.com/pytorch/test-infra/blob/main/aws/lambda/github-status-test/lambda_function.py#L24)
(1) is ok, but (2) raises some questions on why it's needed because its functionalities can be done in PyTorch bot without the need to ask meta-pytorch admins to tweak the repo webhook configs.
github-status-test does several things:
- Upload logs to S3 (and trigger log classifier).
- Archive the raw
workflow_jobandworkflow_runevents, also on S3. - Allow Dev Infra to backfill historical workflow runs and jobs in the event of an outage on our infra. This is rarely used.
Given these 3, should we fold every onto PyTorch bot and deprecate github-status-test? This lambda also has a very bad naming that is hard to get rid off :)
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
No status