Skip to content
代码片段 群组 项目
提交 95476170 编辑于 作者: Fiona Neill's avatar Fiona Neill
浏览文件

Merge branch 'docs-update-keep-artifacts-details' into 'master'

Clarify behavior of keeping latest artifacts

See merge request gitlab-org/gitlab!89499
No related branches found
No related tags found
无相关合并请求
......@@ -375,13 +375,14 @@ job artifacts are deleted.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/229936) in GitLab 13.4.
> - [Made optional with a CI/CD setting](https://gitlab.com/gitlab-org/gitlab/-/issues/241026) in GitLab 13.8.
By default artifacts are always kept for the most recent successful pipeline for
By default artifacts are always kept for successful pipelines for the most recent commit on
each ref. This means that the latest artifacts do not immediately expire according
to the `expire_in` specification.
If a new pipeline for the same ref completes successfully, the previous pipeline's
If a pipeline for a new commit 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.
of the new pipeline are kept automatically. If multiple pipelines run for the most
recent commit on the ref, all artifacts are kept.
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
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册