diff options
| author | Cindy Pallares 🦉 <cindy@gitlab.com> | 2019-05-29 13:31:02 +0000 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-29 13:31:02 +0000 |
| commit | 256d94329ab3f6104f6999c6cb2aef04c7bffb1c (patch) | |
| tree | d39b70887c6d7a2c3f32c29f2d04932c2c98bf1e | |
| parent | 5e5ef31dd520bc9d93e51adc98b8acce43137254 (diff) | |
| download | gitlab-ce-256d94329ab3f6104f6999c6cb2aef04c7bffb1c.tar.gz | |
Add warning about CI traces when enabling S3
Traces may go missing when they're saved in the builds folder and moved
to the local artifacts folder in HA set ups.
| -rw-r--r-- | doc/administration/job_artifacts.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md index e7792106f81..ef370573a98 100644 --- a/doc/administration/job_artifacts.md +++ b/doc/administration/job_artifacts.md @@ -100,6 +100,9 @@ artifacts, you can use an object storage like AWS S3 instead. 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](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 For source installations the following settings are nested under `artifacts:` and then `object_store:`. On omnibus installs they are prefixed by `artifacts_object_store_`. |