GitLab Beta: CI/CD Metrics & Virtual Registry

💡Boost ML CI/CD efficiency with native metrics and multi-registry caching—no extra tools needed.

⚡ 30-Second TL;DR

What Changed

CI/CD analytics adds sortable panel with P50/P95 job durations and failure rates over 30 days

Why It Matters

Speeds up ML pipelines by identifying slow jobs and simplifying multi-registry image pulls, cutting devops overhead for AI teams.

What To Do Next

Enable CI/CD Job Performance Metrics via Analyze > CI/CD analytics in your GitLab project to spot ML pipeline bottlenecks.

Who should care:Enterprise & Security Teams

Web-grounded analysis with 9 cited sources.

•Container Virtual Registry supports configurable cache validity periods defaulting to 24 hours, adjustable to 0 for immutable public registries to optimize performance.
•Top-level groups can define one cleanup policy per group for virtual registries, with execution metrics tracking removals, storage freed, and errors.
•A CVE-2025-12575 Server-Side Request Forgery vulnerability in Virtual Registry was patched in GitLab 18.8.4, 18.7.4, and 18.6.6 releases.
•Virtual registry tokens require 'api' or 'read_virtual_registry' scopes, with access resolved to users who must be group members or admins.

📊 Competitor Analysis▸ Show

Feature	GitLab (18.9)	Harbor	Artifactory	Nexus
Pull-through Cache	✅ Multiple Sources (Beta)	✅ Multiple Sources	✅ Multiple Sources	❌
Maven Virtual Registry	✅ Available	✅ Available	✅ Available	✅
NuGet Virtual Registry	✅ Available	✅ Available	✅ Available	❌
Pricing	Premium/Ultimate tiers	Open Source/Enterprise	Enterprise subscription	Open Source/Enterprise

•Virtual registry proxies and caches images from upstreams like Docker Hub, Harbor, Quay via a single GitLab API endpoint; excludes IAM-auth registries in beta.
•Cache validity configurable per upstream (default 24h, set to 0 for immutable sources); CI/CD job tokens and access tokens with 'api' or 'read_virtual_registry' scopes resolve to group/project members.
•Group-level cleanup policies apply to all virtual registries, monitored via metrics on last/next run, entries removed, storage freed, and errors.
•Beta available on GitLab.com behind feature flag; self-managed requires ClickHouse for analytics; API supports creating/editing upstreams with long-lived tokens.

GitLab will expand virtual registries to Maven, npm, PyPI in FY26

Epic gitlab-com/groups/gitlab-org/-/epics/15088 outlines plans for advanced proxying and caching across additional package formats beyond containers.

Cloud IAM authentication support will be added to virtual registry

GitLab 18.9 release notes track this as an upcoming epic for cloud provider registries currently unsupported in beta.

CI/CD stage-level metrics aggregation will enable pipeline optimization

Article mentions upcoming stage-level features building on job-level P50/P95 durations and failure rates.

2026-02

GitLab 18.9 released with Container Virtual Registry beta for Premium/Ultimate

2026-02

GitLab 18.8.4 patch release fixes CVE-2025-12575 SSFR in Virtual Registry

2025-12

FY26 Package epic initiated for virtual registry support in Maven, npm, PyPI

Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.

Weekly AI Recap

Read this week's curated digest of top AI events →

Same topic

Explore #ci-cd

Same product