diff options
| author | Steve Azzopardi <steveazz@outlook.com> | 2019-02-05 13:53:50 +0100 |
|---|---|---|
| committer | Steve Azzopardi <steveazz@outlook.com> | 2019-02-07 08:44:36 +0100 |
| commit | a60ded42ddc39ba2e94db6dc342c15cf7b2109ae (patch) | |
| tree | b7227e87069988462c49ee9cd074fa54777e3c17 | |
| parent | eeb1197e3de305f1ef29288e7d5b8a2675df7397 (diff) | |
| download | gitlab-ce-docs/update-artifact-expiry.tar.gz | |
Update default expiry information for artifactsdocs/update-artifact-expiry
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.
| -rw-r--r-- | doc/user/project/pipelines/job_artifacts.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/user/project/pipelines/job_artifacts.md b/doc/user/project/pipelines/job_artifacts.md index a8b47558c99..0d0575b1ab4 100644 --- a/doc/user/project/pipelines/job_artifacts.md +++ b/doc/user/project/pipelines/job_artifacts.md @@ -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 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 -[web interface](#browsing-job-artifacts). If you don't define an expiry date, -the artifacts will be kept forever. +[web interface](#browsing-job-artifacts). If the expiry time is not defined, +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 `.gitlab-ci.yml`](../../../ci/yaml/README.md#artifacts). |