summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCindy Pallares 🦉 <cindy@gitlab.com>2019-05-28 14:13:46 +0000
committerCindy Pallares 🦉 <cindy@gitlab.com>2019-05-28 14:13:46 +0000
commit0708a4cf3ca2fa7b5cb47de54314b87aae76c38f (patch)
tree52beec9d9df5582ff503c413f7a9703312dd57f6
parente09823aba5f82a0ad2966b22aa8a9e716b964e8f (diff)
downloadgitlab-ce-docs/warning-about-job-traces-s3.tar.gz
Apply suggestion to doc/administration/job_artifacts.mddocs/warning-about-job-traces-s3
-rw-r--r--doc/administration/job_artifacts.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md
index 909d93a9bfa..ef370573a98 100644
--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -101,7 +101,7 @@ This configuration relies on valid AWS credentials to be configured already.
Use an object storage option like AWS S3 to store job artifacts.
DANGER: **Danger:**
-If you're enabling S3 in GitLab HA, you will need to have a [NFS mount set up for CI traces and artifacts](high_availability/nfs.md#a-single-nfs-mount) or enable [live tracing](job_traces.md#new-live-trace-architecture). If these settings are not set you will risk job traces disappearing or not being saved.
+If you're enabling S3 in [GitLab HA](high_availability/README.md), you will need to have an [NFS mount set up for CI traces and artifacts](high_availability/nfs.md#a-single-nfs-mount) or enable [live tracing](job_traces.md#new-live-trace-architecture). If these settings are not set, you will risk job traces disappearing or not being saved.
### Object Storage Settings