Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,121
    • Issues 43,121
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,382
    • Merge requests 1,382
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #321323
Closed
Open
Created Feb 11, 2021 by Max Orefice@morefice🌀Developer

Keep the most recent PipelineArtifact forever

Problem

As explained on our documentation, our system now keeps the most recent artifact.

By default, the latest artifacts from the most recent successful jobs are never deleted. If a job is configured with expire_in, its artifacts only expire if a more recent artifact exists.

This is not the case for PipelineArtifact which are automatically purged from the system after 1 week.

Proposal

We should refactor our PipelineArtifact purge mechanism to keep the most recent artifact and replicate the same behaviour we have with JobArtifact.

This is currently happening for 2 reports type:

  • CoverageReport
  • CodeQualityMrDiffReport

We could either inherit the same expiration date which is defined at the JobArtifact level or simply keep the most recent artifact by default.

cc @jheimbuck_gl @rickywiens @iamricecake @drew

Edited Feb 24, 2021 by Max Orefice
Assignee
Assign to
Time tracking