Display total CI minutes on pipeline runs

Created on 22 August 2024, 3 months ago

Updated 27 August 2024, 3 months ago

Problem/Motivation

Gitlab shows the wall time for a completely pipeline by default.

See for example this core MR pipeline that finished in 4m55s https://git.drupalcode.org/project/drupal/-/pipelines/261246 (yay) or this one that finished in 8 minutes https://git.drupalcode.org/project/drupal/-/pipelines/260977

However, by default it doesn't show the total CI minutes - e.g. if we have 7 parallel functional test jobs each taking 4 minutes each, that's 28 minutes of runner time, not 4 minutes.

From what I can tell, this feature is implemented in gitlab, but behind a feature flag, see for example these two closed issues.
https://gitlab.com/gitlab-org/gitlab/-/issues/370041
https://gitlab.com/gitlab-org/gitlab/-/issues/376270

However I can't find documentation for it, or a reference to what the exact name of the feature flag is yet.

If we can show this on the pipelines, that would for example allow us to compare how 11.x is doing compared to 10.2.x.

A further step might be to set up monitoring of CI minutes-per-pipeline so we can see if it's going up or down.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Active

Component

GitLab

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.

Test suite performance

Comments & Activities

Issue created by @catch
Comment 3 months ago →
🇺🇸United States drumm NY, US
I’ve only seen GitLab use feature flags for progressively enabling & beta testing functionality; not as another way to configure functionality.

On https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112352 I spotted:

Ensure the project has quota enabled

And on https://docs.gitlab.com/ee/ci/pipelines/compute_minutes.html#set-the-quo...

On self-managed GitLab instances … When enabled, compute quotas apply to private projects only.

So we may currently be out of luck. We are currently monitoring compute usage with some back-end monitoring and alerting. https://gitlab.com/gitlab-org/gitlab/-/issues/351147 ran into bigger refactorings and wasn’t done.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024