Fix object storage support notes
This commit is contained in:
parent
67708aa578
commit
e0cf62d8ae
|
@ -88,13 +88,12 @@ _The artifacts are stored by default in
|
||||||
### Using object storage
|
### Using object storage
|
||||||
|
|
||||||
>**Notes:**
|
>**Notes:**
|
||||||
- [Introduced][ee-1762] in [GitLab Premium][eep] 9.4.
|
- [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1762) in
|
||||||
- Since version 9.5, artifacts are [browsable], when object storage is enabled.
|
[GitLab Premium](https://about.gitlab.com/pricing/) 9.4.
|
||||||
9.4 lacks this feature.
|
- Since version 9.5, artifacts are [browsable](../user/project/pipelines/job_artifacts.md#browsing-artifacts),
|
||||||
> Available in [GitLab Premium](https://about.gitlab.com/pricing/) and
|
when object storage is enabled. 9.4 lacks this feature.
|
||||||
[GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
|
- Since version 10.6, available in [GitLab Core](https://about.gitlab.com/pricing/)
|
||||||
> Since version 10.6, available in [GitLab CE](https://about.gitlab.com/pricing/)
|
- Since version 11.0, we support `direct_upload` to S3.
|
||||||
> Since version 11.0, we support direct_upload to S3.
|
|
||||||
|
|
||||||
If you don't want to use the local disk where GitLab is installed to store the
|
If you don't want to use the local disk where GitLab is installed to store the
|
||||||
artifacts, you can use an object storage like AWS S3 instead.
|
artifacts, you can use an object storage like AWS S3 instead.
|
||||||
|
|
Loading…
Reference in New Issue