Implement monitoring for the mypy wheel build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
I think that at least two mypy releases have been delayed because the mypy wheel build (https://github.com/mypyc/mypy_mypyc-wheels) was broken and nobody noticed it for some time. It would be great if anybody interested in the health of the build could sign up to receive email notifications about build failures.
This blog post may be relevant (not sure though): https://ravgeetdhillon.medium.com/send-an-email-notification-when-github-actions-fails-ea83cbeabbe0
Steps:
- Figure out a way of allowing people for subscribe to notifications (Google group?)
- Implement email notifications
- Break the build on purpose and check that a notification gets sent (both on master and in a release branch)
- Unbreak the build
It would be great if somebody can look into this. If you need access to the wheels repo, please let me know and I can give you the access you'd need.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the mypy_mypyc-wheels repository and its build workflows, with attention to master and release branches. Determine how subscribers, email notifications, and failure checks would be handled, then verify the result by intentionally breaking the build and confirming notifications before restoring it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100