@@ -383,20 +383,15 @@ With this configuration, GitLab adds **artifact 1** as a link to `file.txt` to t
...
@@ -383,20 +383,15 @@ With this configuration, GitLab adds **artifact 1** as a link to `file.txt` to t
{{</history>}}
{{</history>}}
By default artifacts are always kept for successful pipelines for the most recent commit on each ref.
By default, artifacts are always kept for the most recent successful pipeline on each ref. Any `expire_in` configuration does not apply to the most recent artifacts.
Any [`expire_in`](#with-an-expiry) configuration does not apply to the most recent artifacts.
A pipeline's artifacts are only deleted according to the `expire_in` configuration
When a new pipeline on the same ref completes successfully, the previous pipeline's artifacts are deleted according to the `expire_in` configuration. The artifacts of the new pipeline are kept automatically.
if a new pipeline runs for the same ref and:
A pipeline’s artifacts are only deleted according to the `expire_in` configuration if a new pipeline runs for the same ref and:
- Succeeds.
- Succeeds.
- Fails.
- Stops running due to being blocked by a manual job.
- Stops running due to being blocked by a manual job.
Additionally, artifacts are kept for the ref's last successful pipeline even if it
is not the latest pipeline. As a result, if a new pipeline run fails, the last successful pipeline's
artifacts are still kept.
Keeping the latest artifacts can use a large amount of storage space in projects
Keeping the latest artifacts can use a large amount of storage space in projects
with a lot of jobs or large artifacts. If the latest artifacts are not needed in
with a lot of jobs or large artifacts. If the latest artifacts are not needed in
a project, you can disable this behavior to save space:
a project, you can disable this behavior to save space:
