summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-01-08 06:08:13 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-01-08 06:08:13 +0000
commitf6e985dba4d0f5b1ede95e9174d30dd6a8bedf0d (patch)
treec1fed91ae38ad6150ba323a2fc9a68f50f648bb4 /doc
parent30010b161d42bdac3ab5cd16e63cc61c2f4939f3 (diff)
downloadgitlab-ce-f6e985dba4d0f5b1ede95e9174d30dd6a8bedf0d.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r--doc/ci/yaml/README.md17
-rw-r--r--doc/user/project/clusters/serverless/index.md16
2 files changed, 18 insertions, 15 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index e4c45d37e6d..3fc9f75808f 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -2313,6 +2313,23 @@ This example creates three paths of execution:
- Related to the above, stages must be explicitly defined for all jobs
that have the keyword `needs:` or are referred to by one.
+##### Changing the `needs:` job limit
+
+The maximum number of jobs that can be defined within `needs:` defaults to 10, but
+can be changed to 50 via a feature flag. To change the limit to 50,
+[start a Rails console session](https://docs.gitlab.com/omnibus/maintenance/#starting-a-rails-console-session)
+and run:
+
+```ruby
+Feature::disable(:ci_dag_limit_needs)
+```
+
+To set it back to 10, run the opposite command:
+
+```ruby
+Feature::enable(:ci_dag_limit_needs)
+```
+
#### Artifact downloads with `needs`
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/14311) in GitLab v12.6.
diff --git a/doc/user/project/clusters/serverless/index.md b/doc/user/project/clusters/serverless/index.md
index 77981e5bd87..1dc543c3b83 100644
--- a/doc/user/project/clusters/serverless/index.md
+++ b/doc/user/project/clusters/serverless/index.md
@@ -118,8 +118,7 @@ You must do the following:
1. Ensure GitLab can manage Knative:
- For a non-GitLab managed cluster, ensure that the service account for the token
- provided can manage resources in the `serving.knative.dev` API group. It will also
- need list access to the deployments in the `knative-serving` namespace.
+ provided can manage resources in the `serving.knative.dev` API group.
- For a GitLab managed cluster, if you added the cluster in [GitLab 12.1 or later](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/30235),
then GitLab will already have the required access and you can proceed to the next step.
@@ -156,19 +155,6 @@ You must do the following:
- delete
- patch
- watch
- ---
- apiVersion: rbac.authorization.k8s.io/v1
- kind: ClusterRole
- metadata:
- name: gitlab-knative-version-role
- rules:
- - apiGroups:
- - apps
- resources:
- - deployments
- verbs:
- - list
- - get
```
Then run the following command: