Feature Request - Granular Pipeline Artifact Quota Analysis for Storage Optimization

Granular Pipeline Artifact Quota Analysis for Storage Optimization

Summary

A customer reached out (🎫 ticket #681089 ) asking for the below described feature as they are looking to have a better visibility over the pipelines that consume most usage quota.

Need ability to analyze job artifact quota usage at a granular, per-pipeline level across an entire GitLab project to identify storage consumption patterns and optimize quota usage.

Problem Statement

The current Projects API with statistics parameter only provides aggregate storage data and lacks the granular per-pipeline artifact breakdown required for effective storage quota management and optimization.

Requirements

Primary Functionality

  • Analyze job artifact quota usage across all pipelines in a single GitLab project
  • Eliminate need for manual pagination when processing large datasets

Detailed Analysis Capabilities

  • Drill down into granular statistics showing which pipelines consume the most artifact quota
  • Identify patterns of artifacts consuming disproportionate amounts of quota across different pipelines
  • Generate insights for storage waste identification and optimization opportunities

Performance & Scale

  • Handle tens of thousands of pipelines efficiently
  • Avoid API rate limiting/throttling when using script-based solutions
  • Support automated analysis workflows

Use Case

Storage quota management and optimization - Understanding artifact consumption patterns across pipelines to identify waste, optimize storage usage, and make informed decisions about quota allocation and cleanup strategies.

Current Limitations

  • Projects API statistics parameter provides only aggregate storage data
  • No granular per-pipeline artifact breakdown available
  • Manual pagination required for large-scale analysis
  • Risk of API throttling with current script-based approaches

Description was generated using AI

Edited by 🤖 GitLab Bot 🤖