CI infrastructure monitoring #327
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
afnix/infra#327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We've had a few cases recently of CI failing for a while (mostly impacting Lix) due to infrastructure issues. We should figure out a way to alert for:
Probably makes sense to figure this out for Forgejo as well.
Low hanging fruits:
This won't catch more pesky issues like broken DNS resolution inside the agents I'd say (our recent outage)?
For this, I'd like still to count the number of failed builds in a range and alert if there's a statistical anomaly? Not sure how exactly yet.