summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Eastwood <contact@ericeastwood.com>2017-10-05 02:56:52 -0500
committerEric Eastwood <contact@ericeastwood.com>2017-10-05 02:56:52 -0500
commit7b0ca61fe3a03a666d39a388470d5f4e5661b33b (patch)
tree617a47ebe8247a19921ce997d65dcd67d85b2dfd
parent8921af39e74976e37e92c786bd957883110f6522 (diff)
downloadgitlab-ce-7b0ca61fe3a03a666d39a388470d5f4e5661b33b.tar.gz
Clarify where the artifacts metadata .gz is generated
-rw-r--r--doc/administration/job_artifacts.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md
index 3587696225c..86b436d89dd 100644
--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -142,9 +142,9 @@ and [projects APIs](../api/projects.md).
## Implementation details
When GitLab receives an artifacts archive, an archive metadata file is also
-generated. This metadata file describes all the entries that are located in the
-artifacts archive itself. The metadata file is in a binary format, with
-additional GZIP compression.
+generated by [GitLab Workhorse]. This metadata file describes all the entries
+that are located in the artifacts archive itself.
+The metadata file is in a binary format, with additional GZIP compression.
GitLab does not extract the artifacts archive in order to save space, memory
and disk I/O. It instead inspects the metadata file which contains all the