You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using webhook approach, and here is the configuration I used. I expect, latest 10 recent tags and 5 recent branches should get polled, but its not working as expected. Pulling random MRs (not latest 5) and same goes to Tags as well (not latest 10).
Noticed similar behaviour with pull based approach as well, where expecting latest 10 merge-requests, but seeing random MRs
wildcards:
- {}
project_defaults:
output_sparse_status_metrics: true
pull:
pipeline:
jobs:
enabled: true
from_child_pipelines:
enabled: true
aggregation_regexp: ".*"
variables:
enabled: false
refs:
branches:
enabled: true
most_recent: 0
regexp: "^(?:main|master)$"
# If the age of the most recently updated pipeline for the branch is greater than
# this value, the pipeline metrics won't get exported (optional, default: 0 (disabled))
max_age_seconds: 0
tags:
enabled: true
regexp: ".*"
most_recent: 10
# If the age of the most recently updated pipeline for the tag is greater than
# this value, the pipeline metrics won't get exported (optional, default: 0 (disabled))
max_age_seconds: 0
exclude_deleted: true
merge_requests:
enabled: true
most_recent: 5
# If the age of the most recently updated pipeline for the merge request is greater than
# this value, the pipeline metrics won't get exported (optional, default: 0 (disabled))
max_age_seconds: 0
for example, created a new MR and I expect pipeline should appear in the list, but seeing this in the logs, even though pipeline is running
time="2024-11-07T04:11:24Z" level=info msg="received a pipeline webhook from GitLab for a ref, triggering metrics pull" project-name=gt/test ref=42 ref-kind=merge-request
time="2024-11-07T04:11:24Z" level=debug msg="could not find any pipeline for the ref" project-name=gt/test ref=42 ref-kind=merge-request
The text was updated successfully, but these errors were encountered:
I kind of identified issue with Merge Request discrepancy, Seeing above error could not find any pipeline for the ref when the MR is labelled merged results but merge request works fine. This is controlled from Gitlab Merge Request settings
I am using
webhook
approach, and here is the configuration I used. I expect, latest 10 recent tags and 5 recent branches should get polled, but its not working as expected. Pulling random MRs (not latest 5) and same goes to Tags as well (not latest 10).Noticed similar behaviour with pull based approach as well, where expecting latest 10 merge-requests, but seeing random MRs
for example, created a new MR and I expect pipeline should appear in the list, but seeing this in the logs, even though pipeline is running
The text was updated successfully, but these errors were encountered: