Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc/user/gitlab_com/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/gitlab_com/index.md')
-rw-r--r--doc/user/gitlab_com/index.md87
1 files changed, 48 insertions, 39 deletions
diff --git a/doc/user/gitlab_com/index.md b/doc/user/gitlab_com/index.md
index d615b67f3d2..6522f5c4053 100644
--- a/doc/user/gitlab_com/index.md
+++ b/doc/user/gitlab_com/index.md
@@ -31,6 +31,10 @@ gitlab.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
GitLab.com sends emails from the `mg.gitlab.com` domain via [Mailgun](https://www.mailgun.com/) and has
its own dedicated IP address (`198.61.254.240`).
+## Backups
+
+[See our backup strategy](https://about.gitlab.com/handbook/engineering/infrastructure/production/#backups).
+
## Alternative SSH port
GitLab.com can be reached via a [different SSH port](https://about.gitlab.com/blog/2016/02/18/gitlab-dot-com-now-supports-an-alternate-git-plus-ssh-port/) for `git+ssh`.
@@ -78,6 +82,7 @@ Below are the current settings regarding [GitLab CI/CD](../../ci/README.md).
| Scheduled Pipeline Cron | `*/5 * * * *` | `19 * * * *` |
| [Max jobs in active pipelines](../../administration/instance_limits.md#number-of-jobs-in-active-pipelines) | `500` for Free tier, unlimited otherwise | Unlimited
| [Max pipeline schedules in projects](../../administration/instance_limits.md#number-of-pipeline-schedules) | `10` for Free tier, `50` for all paid tiers | Unlimited |
+| [Max number of instance level variables](../../administration/instance_limits.md#number-of-instance-level-variables) | `25` | `25` |
## Repository size limit
@@ -136,7 +141,7 @@ The `gitlab-shared-runners-manager-X.gitlab.com` fleet of Runners are dedicated
Jobs handled by the shared Runners on GitLab.com (`shared-runners-manager-X.gitlab.com`),
**will be timed out after 3 hours**, regardless of the timeout configured in a
-project. Check the issues [4010](https://gitlab.com/gitlab-com/infrastructure/issues/4010) and [4070](https://gitlab.com/gitlab-com/infrastructure/issues/4070) for the reference.
+project. Check the issues [4010](https://gitlab.com/gitlab-com/infrastructure/-/issues/4010) and [4070](https://gitlab.com/gitlab-com/infrastructure/-/issues/4070) for the reference.
Below are the shared Runners settings.
@@ -152,7 +157,7 @@ Below are the shared Runners settings.
Linux Shared Runners on GitLab.com provide a way to run commands in a CI
job before the Runner attempts to run `git init` and `git fetch` to
download a GitLab repository. The
-[pre_clone_script](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section)
+[`pre_clone_script`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section)
can be used for:
- Seeding the build directory with repository data
@@ -219,7 +224,7 @@ sentry_dsn = "X"
"google-tags=gitlab-com,srm",
"google-use-internal-ip",
"google-zone=us-east1-d",
- "engine-opt=mtu=1460", # Set MTU for container interface, for more information check https://gitlab.com/gitlab-org/gitlab-runner/issues/3214#note_82892928
+ "engine-opt=mtu=1460", # Set MTU for container interface, for more information check https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3214#note_82892928
"google-machine-image=PROJECT/global/images/IMAGE",
"engine-opt=ipv6", # This will create IPv6 interfaces in the containers.
"engine-opt=fixed-cidr-v6=fc00::/7",
@@ -243,7 +248,7 @@ During the beta period, the
[shared runner pipeline quota](../admin_area/settings/continuous_integration.md#shared-runners-pipeline-minutes-quota-starter-only)
will apply for groups and projects in the same way as Linux Runners.
This may change when the beta period ends, as discussed in this
-[related issue](https://gitlab.com/gitlab-org/gitlab/issues/30834).
+[related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/30834).
Windows Shared Runners on GitLab.com automatically autoscale by
launching virtual machines on the Google Cloud Platform. This solution uses
@@ -367,7 +372,7 @@ test:
release we will update the autoscaler to enable
the pre-provisioning of virtual machines. This will significantly reduce
the time it takes to provision a VM on the Windows fleet. You can
- follow along in the [related issue](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/issues/32).
+ follow along in the [related issue](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/-/issues/32).
- The Windows Shared Runner fleet may be unavailable occasionally
for maintenance or updates.
- The Windows Shared Runner virtual machine instances do not use the
@@ -415,44 +420,44 @@ different database servers.
The list of GitLab.com specific settings (and their defaults) is as follows:
-| Setting | GitLab.com | Default |
-|:------------------------------------|:--------------------------------------------------------------------|:--------------------------------------|
-| archive_command | `/usr/bin/envdir /etc/wal-e.d/env /opt/wal-e/bin/wal-e wal-push %p` | empty |
-| archive_mode | on | off |
-| autovacuum_analyze_scale_factor | 0.01 | 0.01 |
-| autovacuum_max_workers | 6 | 3 |
-| autovacuum_vacuum_cost_limit | 1000 | -1 |
-| autovacuum_vacuum_scale_factor | 0.01 | 0.02 |
-| checkpoint_completion_target | 0.7 | 0.9 |
-| checkpoint_segments | 32 | 10 |
-| effective_cache_size | 338688MB | Based on how much memory is available |
-| hot_standby | on | off |
-| hot_standby_feedback | on | off |
-| log_autovacuum_min_duration | 0 | -1 |
-| log_checkpoints | on | off |
-| log_line_prefix | `%t [%p]: [%l-1]` | empty |
-| log_min_duration_statement | 1000 | -1 |
-| log_temp_files | 0 | -1 |
-| maintenance_work_mem | 2048MB | 16 MB |
-| max_replication_slots | 5 | 0 |
-| max_wal_senders | 32 | 0 |
-| max_wal_size | 5GB | 1GB |
-| shared_buffers | 112896MB | Based on how much memory is available |
-| shared_preload_libraries | pg_stat_statements | empty |
-| shmall | 30146560 | Based on the server's capabilities |
-| shmmax | 123480309760 | Based on the server's capabilities |
-| wal_buffers | 16MB | -1 |
-| wal_keep_segments | 512 | 10 |
-| wal_level | replica | minimal |
-| statement_timeout | 15s | 60s |
-| idle_in_transaction_session_timeout | 60s | 60s |
+| Setting | GitLab.com | Default |
+|:--------------------------------------|:--------------------------------------------------------------------|:--------------------------------------|
+| `archive_command` | `/usr/bin/envdir /etc/wal-e.d/env /opt/wal-e/bin/wal-e wal-push %p` | empty |
+| `archive_mode` | on | off |
+| `autovacuum_analyze_scale_factor` | 0.01 | 0.01 |
+| `autovacuum_max_workers` | 6 | 3 |
+| `autovacuum_vacuum_cost_limit` | 1000 | -1 |
+| `autovacuum_vacuum_scale_factor` | 0.01 | 0.02 |
+| `checkpoint_completion_target` | 0.7 | 0.9 |
+| `checkpoint_segments` | 32 | 10 |
+| `effective_cache_size` | 338688MB | Based on how much memory is available |
+| `hot_standby` | on | off |
+| `hot_standby_feedback` | on | off |
+| `log_autovacuum_min_duration` | 0 | -1 |
+| `log_checkpoints` | on | off |
+| `log_line_prefix` | `%t [%p]: [%l-1]` | empty |
+| `log_min_duration_statement` | 1000 | -1 |
+| `log_temp_files` | 0 | -1 |
+| `maintenance_work_mem` | 2048MB | 16 MB |
+| `max_replication_slots` | 5 | 0 |
+| `max_wal_senders` | 32 | 0 |
+| `max_wal_size` | 5GB | 1GB |
+| `shared_buffers` | 112896MB | Based on how much memory is available |
+| `shared_preload_libraries` | pg_stat_statements | empty |
+| `shmall` | 30146560 | Based on the server's capabilities |
+| `shmmax` | 123480309760 | Based on the server's capabilities |
+| `wal_buffers` | 16MB | -1 |
+| `wal_keep_segments` | 512 | 10 |
+| `wal_level` | replica | minimal |
+| `statement_timeout` | 15s | 60s |
+| `idle_in_transaction_session_timeout` | 60s | 60s |
Some of these settings are in the process being adjusted. For example, the value
for `shared_buffers` is quite high and as such we are looking into adjusting it.
More information on this particular change can be found at
-<https://gitlab.com/gitlab-com/infrastructure/issues/1555>. An up to date list
+<https://gitlab.com/gitlab-com/infrastructure/-/issues/1555>. An up to date list
of proposed changes can be found at
-<https://gitlab.com/gitlab-com/infrastructure/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=database&label_name[]=change>.
+<https://gitlab.com/gitlab-com/infrastructure/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=database&label_name[]=change>.
## Unicorn
@@ -553,7 +558,7 @@ GitLab.com:
On GitLab.com, projects, groups, and snippets created
As of GitLab 12.2 (July 2019), projects, groups, and snippets have the
-[**Internal** visibility](../../public_access/public_access.md#internal-projects) setting [disabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/issues/12388).
+[**Internal** visibility](../../public_access/public_access.md#internal-projects) setting [disabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/12388).
### SSH maximum number of connections
@@ -563,6 +568,10 @@ If more than the maximum number of allowed connections occur concurrently, they
dropped and users get
[an `ssh_exchange_identification` error](../../topics/git/troubleshooting_git.md#ssh_exchange_identification-error).
+### Import/export
+
+To help avoid abuse, project and group imports, exports, and export downloads are rate limited. See [Project import/export rate limits](../../user/project/settings/import_export.md#rate-limits) and [Group import/export rate limits](../../user/group/settings/import_export.md#rate-limits) for details.
+
## GitLab.com Logging
We use [Fluentd](https://gitlab.com/gitlab-com/runbooks/tree/master/logging/doc#fluentd) to parse our logs. Fluentd sends our logs to
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 12:51:06 +0300