Pipeline Artifact is not taken into account in Project Statistics
Summary
Pipeline Artifacts are not counted against artifacts usage.
Currently we only measure the usage of Job Artifacts. With the introduction of Pipeline Artifacts, we need to determine how we will measure usage and limits of these in conjunction with Job Artifacts.
Before Pipeline artifacts become generally available we must decide how we are going to measure/limit/bucket their usage (#234032 (comment 393229667)).
Proposal
- Create a new column in project_statistics called
pipeline_artifacts_size
- Include UpdateProjectStatistics in PipelineArtifact
- Update project statistics on record creation
update_project_statistics project_statistics_name: :pipeline_artifacts_size
Risks
On-premises users doesn't have information about the pipeline artifact usage. This is useful information for cleaning up the diskspace.
FYI, we recently had a problem on Job Artifact as well #23327 (closed).
Also, our UpdateProjectStatistics
concern is counting up the usage per insertion to the table. Adding this support after GA requires background migration for backfilling data.
Involved components
Optional: Intended side effects
Optional: Missing test coverage
Original Description
The following discussion from !37969 (merged) should be addressed:
-
@ayufan started a discussion: (+4 comments) Should Pipeline Artifact be counted against artifacts usage space similarly how Ci::JobArtifacts is?