diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/instance_limits.md | 14 | ||||
| -rw-r--r-- | doc/api/protected_branches.md | 1 | ||||
| -rw-r--r-- | doc/api/users.md | 1 | ||||
| -rw-r--r-- | doc/ci/docker/using_docker_build.md | 11 | ||||
| -rw-r--r-- | doc/ci/docker/using_docker_images.md | 3 | ||||
| -rw-r--r-- | doc/development/reactive_caching.md | 16 | ||||
| -rw-r--r-- | doc/user/instance_statistics/user_cohorts.md | 1 |
7 files changed, 41 insertions, 6 deletions
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index e1a8ecfdb3f..1ef903f4cf3 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -87,6 +87,20 @@ Plan.default.limits.update!(ci_active_jobs: 500) NOTE: **Note:** Set the limit to `0` to disable it. +## Environment data on Deploy Boards + +[Deploy Boards](../user/project/deploy_boards.md) load information from Kubernetes about +Pods and Deployments. However, data over 10 MB for a certain environment read from +Kubernetes won't be shown. + +## Merge Request reports + +Reports that go over the 20 MB limit won't be loaded. Affected reports: + +- [Merge Request security reports](../user/project/merge_requests/index.md#security-reports-ultimate) +- [CI/CD parameter `artifacts:expose_as`](../ci/yaml/README.md#artifactsexpose_as) +- [JUnit test reports](../ci/junit_test_reports.md) + ## Advanced Global Search limits ### Maximum field length diff --git a/doc/api/protected_branches.md b/doc/api/protected_branches.md index fe950a38b69..e59d7130356 100644 --- a/doc/api/protected_branches.md +++ b/doc/api/protected_branches.md @@ -24,6 +24,7 @@ GET /projects/:id/protected_branches | Attribute | Type | Required | Description | | --------- | ---- | -------- | ----------- | | `id` | integer/string | yes | The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user | +| `search` | string | no | Name or part of the name of protected branches to be searched for | ```shell curl --header "PRIVATE-TOKEN: <your_access_token>" 'https://gitlab.example.com/api/v4/projects/5/protected_branches' diff --git a/doc/api/users.md b/doc/api/users.md index 0e19207f279..601db1c790b 100644 --- a/doc/api/users.md +++ b/doc/api/users.md @@ -1376,6 +1376,7 @@ The activities that update the timestamp are: - Git HTTP/SSH activities (such as clone, push) - User logging in into GitLab - User visiting pages related to Dashboards, Projects, Issues and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/54947) in GitLab 11.8) +- User using the API By default, it shows the activity for all users in the last 6 months, but this can be amended by using the `from` parameter. diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md index b760cd28ea8..ae73957295f 100644 --- a/doc/ci/docker/using_docker_build.md +++ b/doc/ci/docker/using_docker_build.md @@ -217,8 +217,8 @@ support this. # The 'docker' hostname is the alias of the service container as described at # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services. # - # Note that if you're using the Kubernetes executor, the variable - # should be set to tcp://localhost:2376 because of how the + # Note that if you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier, + # the variable must be set to tcp://localhost:2376 because of how the # Kubernetes executor connects services to the job container # DOCKER_HOST: tcp://localhost:2376 # @@ -279,12 +279,11 @@ variables: # The 'docker' hostname is the alias of the service container as described at # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services # - # Note that if you're using the Kubernetes executor, the variable should be set to - # tcp://localhost:2375 because of how the Kubernetes executor connects services - # to the job container + # Note that if you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier, + # the variable must be set to tcp://localhost:2375 because of how the + # Kubernetes executor connects services to the job container # DOCKER_HOST: tcp://localhost:2375 # - # For non-Kubernetes executors, we use tcp://docker:2375 DOCKER_HOST: tcp://docker:2375 # # This will instruct Docker not to start over TLS. diff --git a/doc/ci/docker/using_docker_images.md b/doc/ci/docker/using_docker_images.md index 630beec453c..018e0c4b84d 100644 --- a/doc/ci/docker/using_docker_images.md +++ b/doc/ci/docker/using_docker_images.md @@ -345,6 +345,9 @@ For example, the following two definitions are equal: | `command` | no | 9.4 |Command or script that should be used as the container's command. It will be translated to arguments passed to Docker after the image's name. The syntax is similar to [`Dockerfile`'s `CMD`][cmd] directive, where each shell token is a separate string in the array. | | `alias` | no | 9.4 |Additional alias that can be used to access the service from the job's container. Read [Accessing the services](#accessing-the-services) for more information. | +NOTE: **Note:** +Alias support for the Kubernetes executor was [introduced](https://gitlab.com/gitlab-org/gitlab-runner/issues/2229) in GitLab Runner 12.8, and is only available for Kubernetes version 1.7 or later. + ### Starting multiple services from the same image > Introduced in GitLab and GitLab Runner 9.4. Read more about the [extended diff --git a/doc/development/reactive_caching.md b/doc/development/reactive_caching.md index de93a5aa1d0..94058a3c09c 100644 --- a/doc/development/reactive_caching.md +++ b/doc/development/reactive_caching.md @@ -48,6 +48,12 @@ of the cache by the `reactive_cache_lifetime` value. Once the lifetime has expired, no more background jobs will be enqueued and calling `#with_reactive_cache` will again return `nil` - starting the process all over again. +### 1 MB hard limit + +`ReactiveCaching` has a 1 megabyte default limit. [This value is configurable](#selfreactive_cache_worker_finder). + +If the data we're trying to cache has over 1 megabyte, it will not be cached and a handled `ReactiveCaching::ExceededReactiveCacheLimit` will be notified on Sentry. + ## When to use - If we need to make a request to an external API (for example, requests to the k8s API). @@ -228,6 +234,16 @@ be reset to `reactive_cache_lifetime`. self.reactive_cache_lifetime = 10.minutes ``` +#### `self.reactive_cache_hard_limit` + +- This is the maximum data size that `ReactiveCaching` allows to be cached. +- The default is 1 megabyte. Data that goes over this value will not be cached +and will silently raise `ReactiveCaching::ExceededReactiveCacheLimit` on Sentry. + +```ruby +self.reactive_cache_hard_limit = 5.megabytes +``` + #### `self.reactive_cache_worker_finder` - This is the method used by the background worker to find or generate the object on diff --git a/doc/user/instance_statistics/user_cohorts.md b/doc/user/instance_statistics/user_cohorts.md index 033460f3f73..e664c38a21a 100644 --- a/doc/user/instance_statistics/user_cohorts.md +++ b/doc/user/instance_statistics/user_cohorts.md @@ -26,3 +26,4 @@ How do we measure the activity of users? GitLab considers a user active if: - The user signs in. - The user has Git activity (whether push or pull). - The user visits pages related to Dashboards, Projects, Issues and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/54947) in GitLab 11.8). +- The user uses the API |