Commit a60ded42 authored by Steve Azzopardi's avatar Steve Azzopardi

Update default expiry information for artifacts

We have wrong documentation where we say that if no `expire_in` is set
it will be kept forever, which is not true since we have an instance
wide default expiry date.
parent eeb1197e
...@@ -38,8 +38,9 @@ turn are defined with the `paths` keyword. All paths to files and directories ...@@ -38,8 +38,9 @@ turn are defined with the `paths` keyword. All paths to files and directories
are relative to the repository that was cloned during the build. These uploaded are relative to the repository that was cloned during the build. These uploaded
artifacts will be kept in GitLab for 1 week as defined by the `expire_in` artifacts will be kept in GitLab for 1 week as defined by the `expire_in`
definition. You have the option to keep the artifacts from expiring via the definition. You have the option to keep the artifacts from expiring via the
[web interface](#browsing-job-artifacts). If you don't define an expiry date, [web interface](#browsing-job-artifacts). If the expiry time is not defined,
the artifacts will be kept forever. it defaults to the [instance wide
setting](../../admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only).
For more examples on artifacts, follow the [artifacts reference in For more examples on artifacts, follow the [artifacts reference in
`.gitlab-ci.yml`](../../../ci/yaml/README.md#artifacts). `.gitlab-ci.yml`](../../../ci/yaml/README.md#artifacts).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment