Commit c3a64755 authored by Evan Read's avatar Evan Read Committed by Marcel Amirault

Ensure SSoT for self-managed CI/CD instance limits

parent aaa23f2d
...@@ -353,7 +353,7 @@ displays a list of test suites and cases reported from the XML file. ...@@ -353,7 +353,7 @@ displays a list of test suites and cases reported from the XML file.
![Test Reports Widget](img/pipelines_junit_test_report_v13_10.png) ![Test Reports Widget](img/pipelines_junit_test_report_v13_10.png)
You can view all the known test suites and click on each of these to see further You can view all the known test suites and select each of these to see further
details, including the cases that make up the suite. details, including the cases that make up the suite.
You can also retrieve the reports via the [GitLab API](../api/pipelines.md#get-a-pipelines-test-report). You can also retrieve the reports via the [GitLab API](../api/pipelines.md#get-a-pipelines-test-report).
...@@ -366,8 +366,7 @@ If parsing JUnit report XML results in an error, an indicator is shown next to t ...@@ -366,8 +366,7 @@ If parsing JUnit report XML results in an error, an indicator is shown next to t
![Test Reports With Errors](img/pipelines_junit_test_report_with_errors_v13_10.png) ![Test Reports With Errors](img/pipelines_junit_test_report_with_errors_v13_10.png)
NOTE: For test case parsing limits, see [Max test cases per unit test report](../user/gitlab_com/#gitlab-cicd).
GitLab.com has a 500,000 [test case parsing limit](../user/gitlab_com/#gitlab-cicd). Self-managed administrators can manage this setting on their instance.
GitLab does not parse very [large nodes](https://nokogiri.org/tutorials/parsing_an_html_xml_document.html#parse-options) of JUnit reports. There is [an issue](https://gitlab.com/gitlab-org/gitlab/-/issues/268035) open to make this optional. GitLab does not parse very [large nodes](https://nokogiri.org/tutorials/parsing_an_html_xml_document.html#parse-options) of JUnit reports. There is [an issue](https://gitlab.com/gitlab-org/gitlab/-/issues/268035) open to make this optional.
......
...@@ -55,31 +55,28 @@ can be set at: ...@@ -55,31 +55,28 @@ can be set at:
- The instance level. - The instance level.
- [From GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/21688), the project and group level. - [From GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/21688), the project and group level.
The value is: For the setting on GitLab.com, see [Artifacts maximum size](../../gitlab_com/index.md#gitlab-cicd).
- In *MB* and the default is 100MB per job. The value is in MB and the default is 100MB per job. To change it at the:
- [Set to 1G](../../gitlab_com/index.md#gitlab-cicd) on GitLab.com.
To change it at the:
- Instance level: - Instance level:
1. On the top bar, select **Menu > Admin**. 1. On the top bar, select **Menu > Admin**.
1. On the left sidebar, select **Settings > CI/CD**. 1. On the left sidebar, select **Settings > CI/CD**.
1. Change the value of maximum artifacts size (in MB). 1. Change the value of maximum artifacts size (in MB).
1. Click **Save changes** for the changes to take effect. 1. Select **Save changes** for the changes to take effect.
- Group level (this overrides the instance setting): - Group level (this overrides the instance setting):
1. Go to the group's **Settings > CI/CD > General Pipelines**. 1. Go to the group's **Settings > CI/CD > General Pipelines**.
1. Change the value of **maximum artifacts size (in MB)**. 1. Change the value of **maximum artifacts size (in MB)**.
1. Click **Save changes** for the changes to take effect. 1. Select **Save changes** for the changes to take effect.
- Project level (this overrides the instance and group settings): - Project level (this overrides the instance and group settings):
1. Go to the project's **Settings > CI/CD > General Pipelines**. 1. Go to the project's **Settings > CI/CD > General Pipelines**.
1. Change the value of **maximum artifacts size (in MB)**. 1. Change the value of **maximum artifacts size (in MB)**.
1. Click **Save changes** for the changes to take effect. 1. Select **Save changes** for the changes to take effect.
NOTE: NOTE:
The setting at all levels is only available to GitLab administrators. The setting at all levels is only available to GitLab administrators.
...@@ -94,7 +91,7 @@ and the default value is `30 days`. ...@@ -94,7 +91,7 @@ and the default value is `30 days`.
1. On the top bar, select **Menu > Admin**. 1. On the top bar, select **Menu > Admin**.
1. On the left sidebar, select **Settings > CI/CD**. 1. On the left sidebar, select **Settings > CI/CD**.
1. Change the value of default expiration time. 1. Change the value of default expiration time.
1. Click **Save changes** for the changes to take effect. 1. Select **Save changes** for the changes to take effect.
This setting is set per job and can be overridden in This setting is set per job and can be overridden in
[`.gitlab-ci.yml`](../../../ci/yaml/index.md#artifactsexpire_in). [`.gitlab-ci.yml`](../../../ci/yaml/index.md#artifactsexpire_in).
...@@ -126,7 +123,7 @@ To disable the setting: ...@@ -126,7 +123,7 @@ To disable the setting:
1. On the left sidebar, select **Settings > CI/CD**. 1. On the left sidebar, select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**. 1. Expand **Continuous Integration and Deployment**.
1. Clear the **Keep the latest artifacts for all jobs in the latest successful pipelines** checkbox. 1. Clear the **Keep the latest artifacts for all jobs in the latest successful pipelines** checkbox.
1. Click **Save changes** 1. Select **Save changes**
When you disable the feature, the latest artifacts do not immediately expire. When you disable the feature, the latest artifacts do not immediately expire.
A new pipeline must run before the latest artifacts can expire and be deleted. A new pipeline must run before the latest artifacts can expire and be deleted.
...@@ -156,7 +153,7 @@ After that time passes, the jobs are archived and no longer able to be ...@@ -156,7 +153,7 @@ After that time passes, the jobs are archived and no longer able to be
retried. Make it empty to never expire jobs. It has to be no less than 1 day, retried. Make it empty to never expire jobs. It has to be no less than 1 day,
for example: <code>15 days</code>, <code>1 month</code>, <code>2 years</code>. for example: <code>15 days</code>, <code>1 month</code>, <code>2 years</code>.
As of June 22, 2020 the [value is set](../../gitlab_com/index.md#gitlab-cicd) to 3 months on GitLab.com. Jobs created before that date were archived after September 22, 2020. For the value set for GitLab.com, see [Scheduled job archiving](../../gitlab_com/index.md#gitlab-cicd).
## Protect CI/CD variables by default ## Protect CI/CD variables by default
...@@ -233,7 +230,7 @@ To select a CI/CD template for the required pipeline configuration: ...@@ -233,7 +230,7 @@ To select a CI/CD template for the required pipeline configuration:
1. On the left sidebar, select **Settings > CI/CD**. 1. On the left sidebar, select **Settings > CI/CD**.
1. Expand the **Required pipeline configuration** section. 1. Expand the **Required pipeline configuration** section.
1. Select a CI/CD template from the dropdown. 1. Select a CI/CD template from the dropdown.
1. Click **Save changes**. 1. Select **Save changes**.
## Package Registry configuration ## Package Registry configuration
...@@ -272,7 +269,7 @@ To set the maximum file size: ...@@ -272,7 +269,7 @@ To set the maximum file size:
1. Expand the **Package Registry** section. 1. Expand the **Package Registry** section.
1. Find the package type you would like to adjust. 1. Find the package type you would like to adjust.
1. Enter the maximum file size, in bytes. 1. Enter the maximum file size, in bytes.
1. Click **Save size limits**. 1. Select **Save size limits**.
## Prevent users from registering runners ## Prevent users from registering runners
......
...@@ -133,20 +133,20 @@ Below are the current settings regarding [GitLab CI/CD](../../ci/index.md). ...@@ -133,20 +133,20 @@ Below are the current settings regarding [GitLab CI/CD](../../ci/index.md).
Any settings or feature limits not listed here are using the defaults listed in Any settings or feature limits not listed here are using the defaults listed in
the related documentation. the related documentation.
| Setting | GitLab.com | Default | | Setting | GitLab.com | Default (self-managed) |
|-------------------------------------|-------------|---------| |:-------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Artifacts maximum size (compressed) | 1 GB | 100 MB | | Artifacts maximum size (compressed) | 1 GB | See [Maximum artifacts size](../../user/admin_area/settings/continuous_integration.md#maximum-artifacts-size) |
| Artifacts [expiry time](../../ci/yaml/index.md#artifactsexpire_in) | From June 22, 2020, deleted after 30 days unless otherwise specified (artifacts created before that date have no expiry). | deleted after 30 days unless otherwise specified | | Artifacts [expiry time](../../ci/yaml/index.md#artifactsexpire_in) | From June 22, 2020, deleted after 30 days unless otherwise specified (artifacts created before that date have no expiry). | See [Default artifacts expiration](../admin_area/settings/continuous_integration.md#default-artifacts-expiration) |
| Scheduled Pipeline Cron | `*/5 * * * *` | `3-59/10 * * * *` | | Scheduled Pipeline Cron | `*/5 * * * *` | See [Pipeline schedules advanced configuration](../../administration/cicd.md#change-maximum-scheduled-pipeline-frequency) |
| [Max jobs in active pipelines](../../administration/instance_limits.md#number-of-jobs-in-active-pipelines) | `500` for Free tier, unlimited otherwise | Unlimited | | Maximum jobs in active pipelines | `500` for Free tier, unlimited otherwise | See [Number of jobs in active pipelines](../../administration/instance_limits.md#number-of-jobs-in-active-pipelines) |
| [Max CI/CD subscriptions to a project](../../administration/instance_limits.md#number-of-cicd-subscriptions-to-a-project) | `2` | Unlimited | | Maximum CI/CD subscriptions to a project | `2` | See [Number of CI/CD subscriptions to a project](../../administration/instance_limits.md#number-of-cicd-subscriptions-to-a-project) |
| [Max number of pipeline triggers in a project](../../administration/instance_limits.md#limit-the-number-of-pipeline-triggers) | `25000` for Free tier, Unlimited for all paid tiers | Unlimited | | Maximum number of pipeline triggers in a project | `25000` for Free tier, Unlimited for all paid tiers | See [Limit the number of pipeline triggers](../../administration/instance_limits.md#limit-the-number-of-pipeline-triggers) |
| [Max pipeline schedules in projects](../../administration/instance_limits.md#number-of-pipeline-schedules) | `10` for Free tier, `50` for all paid tiers | Unlimited | | Maximum pipeline schedules in projects | `10` for Free tier, `50` for all paid tiers | See [Number of pipeline schedules](../../administration/instance_limits.md#number-of-pipeline-schedules) |
| [Max pipelines per schedule](../../administration/instance_limits.md#limit-the-number-of-pipelines-created-by-a-pipeline-schedule-per-day) | `24` for Free tier, `288` for all paid tiers | Unlimited | | Maximum pipelines per schedule | `24` for Free tier, `288` for all paid tiers | See [Limit the number of pipelines created by a pipeline schedule per day](../../administration/instance_limits.md#limit-the-number-of-pipelines-created-by-a-pipeline-schedule-per-day) |
| [Scheduled Job Archival](../../user/admin_area/settings/continuous_integration.md#archive-jobs) | 3 months | Never | | Scheduled job archiving | 3 months (from June 22, 2020). Jobs created before that date were archived after September 22, 2020. | Never |
| Max test cases per [unit test report](../../ci/unit_test_reports.md) | `500_000` | Unlimited | | Maximum test cases per [unit test report](../../ci/unit_test_reports.md) | `500000` | Unlimited |
| [Max registered runners](../../administration/instance_limits.md#number-of-registered-runners-per-scope) | Free tier: `50` per-group / `50` per-project <br/> All paid tiers: `1_000` per-group / `1_000` per-project | `1_000` per-group / `1_000` per-project | | Maximum registered runners | Free tier: `50` per-group / `50` per-project<br/>All paid tiers: `1000` per-group / `1000` per-project | See [Number of registered runners per scope](../../administration/instance_limits.md#number-of-registered-runners-per-scope) |
| [Limit dotenv variables](../../administration/instance_limits.md#limit-dotenv-variables) | Free tier: `50` / Premium tier: `100` / Ultimate tier: `150` | 150 | | Limit of dotenv variables | Free tier: `50` / Premium tier: `100` / Ultimate tier: `150` | See [Limit dotenv variables](../../administration/instance_limits.md#limit-dotenv-variables) |
## Package registry limits ## Package registry limits
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment