summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShinya Maeda <shinya@gitlab.com>2018-02-08 04:47:37 +0900
committerShinya Maeda <shinya@gitlab.com>2018-02-08 04:50:46 +0900
commit092a9f333cb8ad461fa9cb0609877266f6a8d8f9 (patch)
tree5b907697ca4ef62348fe25765d97366b688b935a
parentb1f129c589f7d4988976da4eb49e0f349e8338a8 (diff)
downloadgitlab-ce-feature/sm/artifacts-trace-ce-legacy-migration-2.tar.gz
-rw-r--r--doc/administration/job_artifacts.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md
index 33f8a69c249..082527e21b6 100644
--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -92,6 +92,17 @@ AWS S3 to store the artifacts.
[Learn how to use the object storage option.][ee-os]
+### Migrate legacy traces
+
+> Introduced in GitLab 10.5.
+
+From 10.5, each job trace is stored as an artifact. This gives us a lot of
+flexibility, such as uploading traces to ObjectStorage.
+
+Although, legacy traces which had been generated before 10.5 are still
+stored as non-artifact files. To turn those legacy trace files into artifacts,
+run `gitlab-rake gitlab:artifacts:migrate['.']`.
+
## Expiring artifacts
If an expiry date is used for the artifacts, they are marked for deletion