diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-28 09:09:01 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-28 09:09:01 +0300 |
commit | bbf6581214128ae12a6ff32f66a0d03ee57a2e91 (patch) | |
tree | 0da60e8d374831618a6d3fb0a1260d83405ef42b /doc | |
parent | 5cef625594aedbac12011d870719fe81a1587a98 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r-- | doc/administration/instance_limits.md | 14 | ||||
-rw-r--r-- | doc/development/rake_tasks.md | 11 | ||||
-rw-r--r-- | doc/user/analytics/code_review_analytics.md | 10 | ||||
-rw-r--r-- | doc/user/analytics/img/code_review_analytics_v12_8.png | bin | 0 -> 110305 bytes |
4 files changed, 30 insertions, 5 deletions
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index 411563d448c..92ca5c0962d 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -43,6 +43,18 @@ A maximum number of project webhooks applies to each GitLab.com tier. Check the [Maximum number of webhooks (per tier)](../user/project/integrations/webhooks.md#maximum-number-of-webhooks-per-tier) section in the Webhooks page. +To set this limit on a self-hosted installation, run the following in the +[GitLab Rails console](https://docs.gitlab.com/omnibus/maintenance/#starting-a-rails-console-session): + +```ruby +# If limits don't exist for the default plan, you can create one with: +# Plan.default.create_limits! + +Plan.default.limits.update!(project_hooks: 100) +``` + +NOTE: **Note:** Set the limit to `0` to disable it. + ## CI/CD limits ### Number of jobs in active pipelines @@ -73,4 +85,4 @@ To set this limit on a self-hosted installation, run the following in the Plan.default.limits.update!(ci_active_jobs: 500) ``` -Set the limit to `0` to disable it. +NOTE: **Note:** Set the limit to `0` to disable it. diff --git a/doc/development/rake_tasks.md b/doc/development/rake_tasks.md index ff978ee2899..d9b2ace1b5b 100644 --- a/doc/development/rake_tasks.md +++ b/doc/development/rake_tasks.md @@ -54,6 +54,17 @@ By default, this seeds an average of 10 issues per week for the last 52 weeks per project. All issues will also be randomly labeled with team, type, severity, and priority. +#### Seeding groups with sub-groups + +You can seed groups with sub-groups that contain milestones/projects/issues +with the `gitlab:seed:group_seed` task: + +```shell +bin/rake "gitlab:seed:group_seed[subgroup_depth, username]" +``` + +Group are additionally seeded with epics if GitLab instance has epics feature available. + ### Automation If you're very sure that you want to **wipe the current database** and refill diff --git a/doc/user/analytics/code_review_analytics.md b/doc/user/analytics/code_review_analytics.md index 0b501b1a56d..5861afd92a2 100644 --- a/doc/user/analytics/code_review_analytics.md +++ b/doc/user/analytics/code_review_analytics.md @@ -7,17 +7,19 @@ description: "Learn how long your open merge requests have spent in code review, > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/38062) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.7. Code Review Analytics makes it easy to view the longest-running reviews among open merge requests, -enabling you to take action on individual MRs and reduce overall cycle time. +enabling you to take action on individual merge requests and reduce overall cycle time. NOTE: **Note:** Initially, no data will appear. Data is populated as users comment on open merge requests. ## Overview -Code Review Analytics displays a table of open merge requests which are currently considered to be in code review. -The code review period for an MR is automatically identified as the time since the first non-author comment. +Code Review Analytics displays a table of open merge requests that have at least one non-author comment. The review time is measured from the time the first non-author comment was submitted. +The code review period for a merge request is automatically identified as the time since the first non-author comment. -To access Code Review Analytics, from your project's menu, go to **Project Analytics > Code Review**. +To access Code Review Analytics, from your project's menu, go to **{chart}** **Project Analytics > Code Review**. + +![Code Review Analytics](img/code_review_analytics_v12_8.png "List of code reviews; oldest review first.") - The table is sorted by review duration, helping you quickly find the longest-running reviews which may need intervention or to be broken down into smaller parts. - You can filter the list of MRs by milestone and label. diff --git a/doc/user/analytics/img/code_review_analytics_v12_8.png b/doc/user/analytics/img/code_review_analytics_v12_8.png Binary files differnew file mode 100644 index 00000000000..228e03e628a --- /dev/null +++ b/doc/user/analytics/img/code_review_analytics_v12_8.png |