Commit b7bf9a28 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'docs/warning-about-job-traces-s3' into 'master'

Add warning about CI traces when enabling S3

See merge request gitlab-org/gitlab-ce!28734
parents 5e5ef31d 256d9432
...@@ -100,6 +100,9 @@ artifacts, you can use an object storage like AWS S3 instead. ...@@ -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. This configuration relies on valid AWS credentials to be configured already.
Use an object storage option like AWS S3 to store job artifacts. 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 ### 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_`. For source installations the following settings are nested under `artifacts:` and then `object_store:`. On omnibus installs they are prefixed by `artifacts_object_store_`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment