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
Is your feature request related to a problem? Please describe.
When using the metric CI-pipeline duration with GitLab as source, and configuring scheduled pipeline runs, GitLab may return multiple pipelines and it is not possible to further select a specific pipeline.
Describe the solution you'd like
A possibility to filter (scheduled) pipelines by description.
Also include the matched pipelines in the measurement entities.
Additional context
Unfortunately, the pipelines endpoints do not include the schedule id in the responses. So, to know which pipeline was triggered by which schedule, we need to retrieve the schedules via the schedules endpoint and then get the pipelines scheduled by the schedule via the pipelines triggered by a pipeline schedule endpoint.
The scheduled pipelines response includes the pipeline schedule description, so users can use that to filter schedules. No need to use the schedule id.
The text was updated successfully, but these errors were encountered:
fniessink
changed the title
filter specific scheduled pipelines for metric CI-pipeline duration
Filter specific scheduled pipelines for metric CI-pipeline duration
Dec 11, 2024
fniessink
changed the title
Filter specific scheduled pipelines for metric CI-pipeline duration
Filter specific pipelines for metric CI-pipeline duration
Dec 11, 2024
Is your feature request related to a problem? Please describe.
When using the metric CI-pipeline duration with GitLab as source, and configuring scheduled pipeline runs, GitLab may return multiple pipelines and it is not possible to further select a specific pipeline.
Describe the solution you'd like
A possibility to filter (scheduled) pipelines by description.
Also include the matched pipelines in the measurement entities.
Additional context
Unfortunately, the pipelines endpoints do not include the schedule id in the responses. So, to know which pipeline was triggered by which schedule, we need to retrieve the schedules via the schedules endpoint and then get the pipelines scheduled by the schedule via the pipelines triggered by a pipeline schedule endpoint.
The scheduled pipelines response includes the pipeline schedule description, so users can use that to filter schedules. No need to use the schedule id.
The text was updated successfully, but these errors were encountered: