-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline Status - Passed with Warnings #123
Comments
thanks for kind feedback @jayyzhao! Indeed, I reckon it would be possible by matching out if the job was manual or not 🤔 |
Based on https://gitlab.com/gitlab-org/gitlab/-/issues/229137 , maybe it is possible to perform a request to the pipeline itself and look for the |
Given that there is already an individual API call for each pipeline, the status metric could be based on the gitlab-ci-pipelines-exporter/pkg/schemas/pipelines.go Lines 75 to 82 in 484359a
this could be something like this: return Pipeline{
ID: gp.ID,
Coverage: coverage,
Timestamp: timestamp,
DurationSeconds: float64(gp.Duration),
QueuedDurationSeconds: float64(gp.QueuedDuration),
// Status: gp.DetailedStatus.Group,
Status: gp.DetailedStatus.Text,
} |
Great stuff love the work. An enhancement would be able to include the differentiation of status Passed/Successful with Passed with Warning.
The text was updated successfully, but these errors were encountered: