Goal Maintain artifacts for downstream pipelines while respecting the configured expiration period. Constraints & Uncertainty GitLab allows expiration to be set globally, per-pipeline, or per-job. It is unclear whether artifacts referenced by downstream jobs are exempt from the same expiration rules or if they inherit the same policy as the originating job. Questions When an artifact is configured to expire after 30 days, does GitLab automatically delete it from downstream pipelines that reference it? Can the retention period be configured separately for artifacts that are pulled by downstream jobs? Is there an API endpoint to query the expiration status of an artifact before it is purged?

GitLab Artifact Expiration: Downstream Artifact Deletion Uncertainty

Artifact expiration policy silently deletes downstream artifacts after pipeline completion

0 reputation · 08 May 2020, 07:02 UTC

98.5K views0

Goal

Maintain artifacts for downstream pipelines while respecting the configured expiration period.

Constraints & Uncertainty

GitLab allows expiration to be set globally, per-pipeline, or per-job. It is unclear whether artifacts referenced by downstream jobs are exempt from the same expiration rules or if they inherit the same policy as the originating job.

Questions

When an artifact is configured to expire after 30 days, does GitLab automatically delete it from downstream pipelines that reference it?
Can the retention period be configured separately for artifacts that are pulled by downstream jobs?
Is there an API endpoint to query the expiration status of an artifact before it is purged?

4,663 following

Keep exploring this topic

Canceling a parent pipeline: are downstream pipelines left running?

GitLab's pipeline cancel API targets one pipeline at a time; whether cancellation should cascade to downstream pipelines is undefined for automation callers.

Protected CI/CD Variables Missing in Production Pipeline

A pipeline that succeeds locally fails in production because protected CI/CD variables may be missing or masked. Identify branch protection, masking rules, and runner scope to diagnose the issue.

Helm local index cache interaction with CI/CD chart deployment

Helm’s local index cache lacks TTL, risking stale chart versions in CI/CD pipelines; how can automatic refresh be ensured?

Content collection validation warnings exit zero in CI despite validate: 'warn'

Astro's validate: 'warn' for content collections exits 0, letting schema violations pass CI. No structured diagnostics or stable warning codes exist to filter and fail selectively.

Artifact expiration policy silently deletes downstream artifacts after pipeline completion

Goal

Constraints & Uncertainty

Questions

0 answers

Your perspective belongs here.

0 question comments