🕷️
SetupAI
EN
🦊較早收集於 15h

GitLab Beta：CI/CD 指標與虛擬註冊表

GitLab Beta：CI/CD 指標與虛擬註冊表
PostLinkedIn
🦊閱讀原文： GitLab Blog
#ci-cd#container-registry#devopsgitlabgitlabclickhouse

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

⚡ 30-Second TL;DR

有什麼變化

CI/CD 分析新增可排序面板，顯示 30 天內 P50/P95 工作持續時間與失敗率

為什麼重要

透過辨識緩慢工作並簡化多註冊表映像拉取，加速 ML 管線，減少 AI 團隊的 DevOps 開銷。

下一步行動

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

誰應關注：Enterprise & Security Teams

關鍵要點

  • •CI/CD 分析新增可排序面板，顯示 30 天內 P50/P95 工作持續時間與失敗率
  • •Container Virtual Registry 建立單一 GitLab 端點，從 Docker Hub、Harbor、Quay 拉取/快取
  • •GitLab.com 有限 Beta；自管需配置 ClickHouse
  • •即將推出建置/測試/部署階段層級彙總

🧠 深度解析

背景與延伸：來自公開資料，非原文內容。引用 9 個來源。

🔑 增強重點摘要

  • •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.
📊 競品分析▸ Show
FeatureGitLab (18.9)HarborArtifactoryNexus
Pull-through Cache✅ Multiple Sources (Beta)✅ Multiple Sources✅ Multiple Sources❌
Maven Virtual Registry✅ Available✅ Available✅ Available✅
NuGet Virtual Registry✅ Available✅ Available✅ Available❌
PricingPremium/Ultimate tiersOpen Source/EnterpriseEnterprise subscriptionOpen 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.

🔮 前景展望AI analysis grounded in cited sources

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
🦊閱讀原文： GitLab Blog
📰

AI 週報

閱讀本週精選 AI 大事摘要 →

👉相關動態

同主題

探索 #ci-cd

同產品

更多關於 gitlab

同來源

最新來自 GitLab Blog

AI 策展新聞聚合。所有內容版權歸原始發布者所有。
原始來源： GitLab Blog ↗

這是摘要，不是原文。去看原站，或訂閱每週簡報。

每週 AI 簡報

每週一封，可隨時退訂。