Merge branch 'docs-its-relative-10' into 'master'
Change several links to relative See merge request gitlab-org/gitlab-ce!32919
This commit is contained in:
commit
aa8f87f4ff
|
@ -64,7 +64,7 @@ Array.methods.grep(/sing/)
|
|||
|
||||
## Find method source
|
||||
|
||||
Works for [non-instrumented methods](https://docs.gitlab.com/ce/development/instrumentation.html#checking-instrumented-methods):
|
||||
Works for [non-instrumented methods](../../development/instrumentation.md#checking-instrumented-methods):
|
||||
|
||||
```ruby
|
||||
instance_of_object.method(:foo).source_location
|
||||
|
@ -474,7 +474,7 @@ User.active.count
|
|||
```
|
||||
|
||||
```bash
|
||||
# Using curl and jq (up to a max 100, see [pagination](https://docs.gitlab.com/ee/api/#pagination)
|
||||
# Using curl and jq (up to a max 100, see pagination docs https://docs.gitlab.com/ee/api/#pagination
|
||||
curl --silent --header "Private-Token: ********************" "https://gitlab.example.com/api/v4/users?per_page=100&active" | jq --compact-output '.[] | [.id,.name,.username]'
|
||||
```
|
||||
|
||||
|
@ -744,7 +744,7 @@ build.dependencies.each do |d| { puts "status: #{d.status}, finished at: #{d.fin
|
|||
|
||||
### Disable strict artifact checking (Introduced in GitLab 10.3.0)
|
||||
|
||||
See <https://docs.gitlab.com/ee/administration/job_artifacts.html#validation-for-dependencies>.
|
||||
See [job artifacts documentation](../job_artifacts.md#validation-for-dependencies).
|
||||
|
||||
```ruby
|
||||
Feature.enable('ci_disable_validates_dependencies')
|
||||
|
|
|
@ -177,7 +177,7 @@ and they will assist you with any issues you are having.
|
|||
```
|
||||
|
||||
After <https://gitlab.com/gitlab-org/charts/gitlab/issues/780> is fixed, it should
|
||||
be possible to use [Updating GitLab using the Helm Chart](https://docs.gitlab.com/ee/install/kubernetes/gitlab_chart.html#updating-gitlab-using-the-helm-chart)
|
||||
be possible to use [Updating GitLab using the Helm Chart](https://docs.gitlab.com/charts/index.html#updating-gitlab-using-the-helm-chart)
|
||||
for upgrades.
|
||||
|
||||
- How to apply changes to GitLab config:
|
||||
|
@ -244,7 +244,7 @@ to those documents for details.
|
|||
on your workstation.
|
||||
|
||||
- When all the pods show either a `Running` or `Completed` status, get the GitLab password as
|
||||
described in [Initial login](https://docs.gitlab.com/ee/install/kubernetes/gitlab_chart.html#initial-login),
|
||||
described in [Initial login](https://docs.gitlab.com/charts/installation/deployment.html#initial-login),
|
||||
and log in to GitLab via the UI. It will be accessible via `https://gitlab.domain`
|
||||
where `domain` is the value provided in the yaml file.
|
||||
|
||||
|
|
|
@ -259,7 +259,7 @@ then compare summaries of both results and dive into the differences.
|
|||
Rough numbers for calls to `open` and `openat` (used to access files) on various configurations.
|
||||
Slow storage can cause the dreaded `DeadlineExceeded` error in Gitaly.
|
||||
|
||||
Also [see this entry](https://docs.gitlab.com/ee/administration/operations/filesystem_benchmarking.html)
|
||||
Also [see this entry](../operations/filesystem_benchmarking.md)
|
||||
in the handbook for quick tests customers can perform to check their filesystem performance.
|
||||
|
||||
Keep in mind that timing information from `strace` is often somewhat inaccurate, so
|
||||
|
|
|
@ -23,7 +23,7 @@ but contributions are welcome.
|
|||
|
||||
### GitLab
|
||||
|
||||
Please see [our Docker test environment docs](https://docs.gitlab.com/ee/install/digitaloceandocker.html#create-new-gitlab-container)
|
||||
Please see [our Docker test environment docs](../../install/digitaloceandocker.md#create-new-gitlab-container)
|
||||
for how to run GitLab on Docker. When spinning this up with `docker-machine`, ensure
|
||||
you change a few things:
|
||||
|
||||
|
@ -59,7 +59,7 @@ docker run --name gitlab_saml -p 8080:8080 -p 8443:8443 \
|
|||
-d jamedjo/test-saml-idp
|
||||
```
|
||||
|
||||
The following will also need to go in your `/etc/gitlab/gitlab.rb`. See [our SAML docs](https://docs.gitlab.com/ee/integration/saml.html)
|
||||
The following will also need to go in your `/etc/gitlab/gitlab.rb`. See [our SAML docs](../../integration/saml.md)
|
||||
for more, as well as the list of [default usernames, passwords, and emails](https://hub.docker.com/r/jamedjo/test-saml-idp/#usage).
|
||||
|
||||
```ruby
|
||||
|
|
|
@ -580,7 +580,7 @@ For private and internal projects:
|
|||
If you want to use your own Docker images for docker-in-docker there are a few things you need to do in addition to the steps in the [docker-in-docker](#use-docker-in-docker-workflow-with-docker-executor) section:
|
||||
|
||||
1. Update the `image` and `service` to point to your registry.
|
||||
1. Add a service [alias](https://docs.gitlab.com/ee/ci/yaml/#servicesalias).
|
||||
1. Add a service [alias](../yaml/README.md#servicesalias).
|
||||
|
||||
Below is an example of what your `.gitlab-ci.yml` should look like,
|
||||
assuming you have it configured with [TLS enabled](#tls-enabled):
|
||||
|
|
|
@ -2089,7 +2089,7 @@ staging:
|
|||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23464) in GitLab 12.3.
|
||||
|
||||
`interruptible` is used to indicate that a job should be canceled if made redundant by a newer run of the same job. Defaults to `true`.
|
||||
This value will only be used if the [automatic cancellation of redundant pipelines feature](https://docs.gitlab.com/ee/user/project/pipelines/settings.html#auto-cancel-pending-pipelines)
|
||||
This value will only be used if the [automatic cancellation of redundant pipelines feature](../../user/project/pipelines/settings.md#auto-cancel-pending-pipelines)
|
||||
is enabled.
|
||||
|
||||
When enabled, a pipeline on the same branch will be canceled when:
|
||||
|
|
|
@ -115,7 +115,7 @@ To subscribe to GitLab through a self-managed installation:
|
|||
|
||||
1. [Install](https://about.gitlab.com/install/) GitLab.
|
||||
1. Complete the installation with
|
||||
[administration tasks](https://docs.gitlab.com/ee/administration/).
|
||||
[administration tasks](../administration/index.md).
|
||||
1. Select the **Starter**, **Premium**, or **Ultimate** self-managed plan
|
||||
through the [GitLab Subscription Manager](https://customers.gitlab.com/).
|
||||
1. Apply your license file. After purchase, a license file is sent to the email
|
||||
|
|
Loading…
Reference in New Issue