Annotate failing jobs
n
nic.girault@gmail.com
Teams performing continuous improvement on a daily basis can be interested in understanding why their tests are failing and improving this metric. It would be great to be able to annotate failing workflows or jobs with tags or/and notes to help teams to spot failure patterns. An graph in the insights page would be a nice to have.
Autopilot
Merged in a post:
Manual Annotations for Job Failures
H
Henna Abbas
Problem:
When jobs fail in CircleCI, there's no way to leave contextual notes explaining why it happened or linking to relevant resources. This leads to repeated investigations, lost knowledge, and wasted time searching for context.
Proposed Solution:
Add manual annotations on graphs and job timelines (similar to Datadog's annotations) that allow users to:
* Pin notes to specific job failures
* Add explanations and links (e.g., to Datadog graphs, PRs, tickets)
* Make context visible to all team members
Use Case:
Team has a non-blocking job integration-tests still in development. When it fails, they want to annotate: "Failed due to API rate limiting. See [DD graph]. Will be fixed in Q1. Safe to ignore."
This prevents others from re-investigating the same issue and creates a historical record of patterns.
Benefits:
* Reduced investigation time
* Better knowledge sharing across the team
* Historical visibility of recurring issues
* Improved incident response
P
Patrick Fletcher
@ geometry dash lite: This idea sounds amazing. Hope that it will be considered.
o
online.cockbill@gmail.com
Also agree that this would be nice on CircleCI! A very useful feature I have used in other continuous integration environments.
L
Liam Sharp
Agreed. Each morning we go through our overnight soak tests and investigate any failures. It would be nice to be able to annotate these so we know what has and hasn't been looked at. We've moved to CircleCI from Jenkins and it has this feature.