# Predefined environment variables reference
> 原文：[https://docs.gitlab.com/ee/ci/variables/predefined_variables.html](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html)
# Predefined environment variables reference[](#predefined-environment-variables-reference "Permalink")
有关此主题的介绍，请通读[环境变量入门](README.html)文档.
仅当使用最低版本的[GitLab Runner 时，](https://docs.gitlab.com/runner/)某些预定义的环境变量才可用. 请查阅下表以查找所需的 Runner 版本.
**注意：**从 GitLab 9.0 开始，我们已弃用了一些变量. 阅读[9.0 重命名](deprecated_variables.html#gitlab-90-renamed-variables)部分以查找其替换内容. **强烈建议您使用新变量，因为我们将在以后的 GitLab 版本中删除旧变量.**
您可以在`.gitlab-ci.yml`文件中添加命令，以[输出可用于作业的所有变量的值](README.html#list-all-environment-variables) .
Kubernetes 特定于环境的环境变量在[Kubernetes 部署变量](../../user/project/clusters/index.html#deployment-variables)部分中进行了详细介绍.
| Variable | GitLab | Runner | Description |
| --- | --- | --- | --- |
| `CHAT_CHANNEL` | 10.6 | all | 触发[ChatOps](../chatops/README.html)命令的源聊天通道 |
| `CHAT_INPUT` | 10.6 | all | 在[ChatOps](../chatops/README.html)命令中传递的其他参数 |
| `CI` | all | 0.4 | 标记作业在 CI 环境中执行 |
| `CI_API_V4_URL` | 11.7 | all | GitLab API v4 根 URL |
| `CI_BUILDS_DIR` | all | 11.10 | 执行构建的顶级目录. |
| `CI_COMMIT_BEFORE_SHA` | 11.2 | all | 先前的最新提交存在于分支中. 合并请求的管道中始终为`0000000000000000000000000000000000000000` |
| `CI_COMMIT_DESCRIPTION` | 10.8 | all | 提交的描述：如果标题少于 100 个字符，则不带第一行的消息； 在其他情况下为完整消息. |
| `CI_COMMIT_MESSAGE` | 10.8 | all | 完整的提交消息. |
| `CI_COMMIT_REF_NAME` | 9.0 | all | 构建项目的分支或标记名称 |
| `CI_COMMIT_REF_PROTECTED` | 11.11 | all | 如果作业在受保护的引用上运行，则为`true`否则为`false` |
| `CI_COMMIT_REF_SLUG` | 9.0 | all | `$CI_COMMIT_REF_NAME`小写，缩短为 63 个字节，并且将`0-9`和`az`以外的所有内容替换为`-` . 没有前导/尾随`-` . 在 URL，主机名和域名中使用. |
| `CI_COMMIT_SHA` | 9.0 | all | 为其构建项目的提交修订 |
| `CI_COMMIT_SHORT_SHA` | 11.7 | all | `CI_COMMIT_SHA`的前八个字符 |
| `CI_COMMIT_BRANCH` | 12.6 | 0.5 | 提交分支名称. 仅在建立分支时显示. |
| `CI_COMMIT_TAG` | 9.0 | 0.5 | 提交标记名称. 仅在构建标签时显示. |
| `CI_COMMIT_TITLE` | 10.8 | all | 提交的标题-消息的第一行 |
| `CI_CONCURRENT_ID` | all | 11.10 | 单个执行程序中生成执行的唯一 ID. |
| `CI_CONCURRENT_PROJECT_ID` | all | 11.10 | 单个执行程序和项目中生成执行的唯一 ID. |
| `CI_CONFIG_PATH` | 9.4 | 0.5 | CI 配置文件的路径. 默认为`.gitlab-ci.yml` |
| `CI_DEBUG_TRACE` | all | 1.7 | 是否启用[调试日志记录（跟踪）](README.html#debug-logging) |
| `CI_DEFAULT_BRANCH` | 12.4 | all | 项目的默认分支的名称. |
| `CI_DEPLOY_PASSWORD` | 10.8 | all | [GitLab Deploy 令牌的](../../user/project/deploy_tokens/index.html#gitlab-deploy-token)身份验证密码，仅在项目具有相关性时才提供. |
| `CI_DEPLOY_USER` | 10.8 | all | [GitLab Deploy 令牌的](../../user/project/deploy_tokens/index.html#gitlab-deploy-token)身份验证用户名，仅在项目具有相关性时才存在. |
| `CI_DISPOSABLE_ENVIRONMENT` | all | 10.1 | 标记作业是在一次性环境中执行的（仅为该作业创建并在执行后处置/销毁的东西-除`shell`和`ssh`以外的所有执行程序）. 如果环境是一次性的，则将其设置为 true，否则将完全未定义. |
| `CI_ENVIRONMENT_NAME` | 8.15 | all | 该作业的环境名称. 仅在设置了[`environment:name`](../yaml/README.html#environmentname)存在. |
| `CI_ENVIRONMENT_SLUG` | 8.15 | all | 环境名称的简化版本，适合包含在 DNS，URL，Kubernetes 标签等中.仅在设置了[`environment:name`](../yaml/README.html#environmentname)存在. |
| `CI_ENVIRONMENT_URL` | 9.3 | all | 该作业的环境的 URL. 仅当设置了[`environment:url`](../yaml/README.html#environmenturl)时才存在. |
| `CI_EXTERNAL_PULL_REQUEST_IID` | 12.3 | all | 如果[管道用于外部请求，](../ci_cd_for_external_repos/index.html#pipelines-for-external-pull-requests)则来自 GitHub 的请求请求 ID. 仅在以下情况`only: [external_pull_requests]`可用`only: [external_pull_requests]`或[`rules`](../yaml/README.html#rules)语法，并且拉取请求处于打开状态. |
| `CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME` | 12.3 | all | 如果[管道用于外部](../ci_cd_for_external_repos/index.html#pipelines-for-external-pull-requests)请求，则请求请求的源分支名称. 仅在以下情况`only: [external_pull_requests]`可用`only: [external_pull_requests]`或[`rules`](../yaml/README.html#rules)语法，并且拉取请求处于打开状态. |
| `CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_SHA` | 12.3 | all | 如果[管道用于外部](../ci_cd_for_external_repos/index.html#pipelines-for-external-pull-requests)请求，则请求请求的源分支的 HEAD SHA. 仅在以下情况`only: [external_pull_requests]`可用`only: [external_pull_requests]`或[`rules`](../yaml/README.html#rules)语法，并且拉取请求处于打开状态. |
| `CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_NAME` | 12.3 | all | 如果[管道用于外部](../ci_cd_for_external_repos/index.html#pipelines-for-external-pull-requests)请求，则请求请求的目标分支名称. 仅在以下情况`only: [external_pull_requests]`可用`only: [external_pull_requests]`或[`rules`](../yaml/README.html#rules)语法，并且拉取请求处于打开状态. |
| `CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_SHA` | 12.3 | all | 如果[管道用于外部](../ci_cd_for_external_repos/index.html#pipelines-for-external-pull-requests)请求，则请求请求目标分支的 HEAD SHA. 仅在以下情况`only: [external_pull_requests]`可用`only: [external_pull_requests]`或[`rules`](../yaml/README.html#rules)语法，并且拉取请求处于打开状态. |
| `CI_HAS_OPEN_REQUIREMENTS` | 13.1 | all | 仅当管道的项目有任何开放[要求时，](../../user/project/requirements/index.html)才将值包括为`true` . 如果管道项目没有开放要求，则不包括在内. |
| `CI_JOB_ID` | 9.0 | all | GitLab CI / CD 在内部使用的当前作业的唯一 ID |
| `CI_JOB_IMAGE` | 12.9 | 12.9 | 运行 CI 作业的图像的名称 |
| `CI_JOB_MANUAL` | 8.12 | all | 指示作业已手动启动的标志 |
| `CI_JOB_NAME` | 9.0 | 0.5 | `.gitlab-ci.yml`定义的作业名称 |
| `CI_JOB_STAGE` | 9.0 | 0.5 | `.gitlab-ci.yml`定义的阶段名称 |
| `CI_JOB_TOKEN` | 9.0 | 1.2 | 用于通过[GitLab 容器注册表](../../user/packages/container_registry/index.html)进行身份验证，下载[从属存储库](../../user/project/new_ci_build_permissions_model.html#dependent-repositories)以及访问[GitLab 管理的 Terraform 状态的](../../user/infrastructure/index.html#gitlab-managed-terraform-state)令牌. |
| `CI_JOB_JWT` | 12.10 | all | RS256 JSON Web 令牌，可用于与支持 JWT 身份验证的第三方系统进行身份验证，例如[HashiCorp 的 Vault](../examples/authenticating-with-hashicorp-vault) . |
| `CI_JOB_URL` | 11.1 | 0.5 | 职位详情网址 |
| `CI_KUBERNETES_ACTIVE` | 13.0 | all | Included with the value `true` only if the pipeline has a Kubernetes cluster available for deployments. Not included if no cluster is available. Can be used as an alternative to [`only:kubernetes`/`except:kubernetes`](../yaml/README.html#onlykubernetesexceptkubernetes) with [`rules:if`](../yaml/README.html#rulesif) |
| `CI_MERGE_REQUEST_ASSIGNEES` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则该合并请求的受让人的用户名列表用逗号分隔. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_ID` | 11.6 | all | 合并请求的项目级别 ID. 仅当[管道用于合并请求](../merge_request_pipelines/index.html)并且创建[合并请求](../merge_request_pipelines/index.html)时才可用. |
| `CI_MERGE_REQUEST_IID` | 11.6 | all | 合并请求的实例级 IID. 仅[当管道用于合并请求](../merge_request_pipelines/index.html)并且创建[合并请求](../merge_request_pipelines/index.html)时才可用. |
| `CI_MERGE_REQUEST_LABELS` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的逗号分隔标签名称. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_MILESTONE` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的里程碑标题. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_PROJECT_ID` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的项目的 ID. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_PROJECT_PATH` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的项目路径（例如， `namespace/awesome-project` ）. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_PROJECT_URL` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的项目的 URL（例如`http://192.168.10.15:3000/namespace/awesome-project` ）. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_REF_PATH` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的 ref 路径. （例如`refs/merge-requests/1/head` ）. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_SOURCE_BRANCH_NAME` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的源分支名称. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_SOURCE_BRANCH_SHA` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的源分支的 HEAD SHA. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法，创建合并请求，并且管道是[合并结果管道](../merge_request_pipelines/pipelines_for_merged_results/index.html) . |
| `CI_MERGE_REQUEST_SOURCE_PROJECT_ID` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的源项目的 ID. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_SOURCE_PROJECT_PATH` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的源项目的路径. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_SOURCE_PROJECT_URL` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的源项目的 URL. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_TARGET_BRANCH_NAME` | 11.6 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的目标分支名称. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_TARGET_BRANCH_SHA` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的目标分支的 HEAD SHA. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法，创建合并请求，并且管道是[合并结果管道](../merge_request_pipelines/pipelines_for_merged_results/index.html) . |
| `CI_MERGE_REQUEST_TITLE` | 11.9 | all | 如果[管道用于合并请求](../merge_request_pipelines/index.html) ，则合并请求的标题. 仅在以下情况`only: [merge_requests]`可用：仅使用`only: [merge_requests]`或[`rules`](../yaml/README.html#rules)语法并创建合并请求. |
| `CI_MERGE_REQUEST_EVENT_TYPE` | 12.3 | all | 合并请求的事件类型（如果[管道用于合并请求）](../merge_request_pipelines/index.html) . 可以`detached` ， `merged_result`或`merge_train` . |
| `CI_NODE_INDEX` | 11.5 | all | 作业在作业集中的索引. 如果作业未并行化，则不会设置此变量. |
| `CI_NODE_TOTAL` | 11.5 | all | Total number of instances of this job running in parallel. If the job is not parallelized, this variable is set to `1`. |
| `CI_PAGES_DOMAIN` | 11.8 | all | 托管 GitLab 页面的已配置域. |
| `CI_PAGES_URL` | 11.8 | all | GitLab 页面构建页面的 URL. 始终属于`CI_PAGES_DOMAIN`的子域. |
| `CI_PIPELINE_ID` | 8.10 | all | GitLab CI / CD 在内部使用的当前管道的唯一 ID |
| `CI_PIPELINE_IID` | 11.0 | all | 当前管道的唯一 ID 范围为项目 |
| `CI_PIPELINE_SOURCE` | 10.0 | all | 指示如何触发管道. 可能的选项是： `push` ， `web` ， `schedule` ， `api` ， `external` ， `chat` ， `webide` ， `merge_request_event` ， `external_pull_request_event` ， `parent_pipeline` ， [`trigger`或`pipeline`](../triggers/README.html#authentication-tokens) （自 13.0 起改名为`cross_project_pipeline` ）. 对于在 GitLab 9.5 之前创建的管道，这将显示为`unknown` . |
| `CI_PIPELINE_TRIGGERED` | all | all | 指示已[触发](../triggers/README.html)作业的标志 |
| `CI_PIPELINE_URL` | 11.1 | 0.5 | 管道详细资料网址 |
| `CI_PROJECT_DIR` | all | all | 克隆存储库以及运行作业的完整路径. 如果设置了 GitLab Runner 的`builds_dir`参数，则相对于`builds_dir`的值设置此变量. 有关更多信息，请参见 GitLab Runner 的[高级配置](https://docs.gitlab.com/runner/configuration/advanced-configuration.html) . |
| `CI_PROJECT_ID` | all | all | GitLab CI / CD 在内部使用的当前项目的唯一 ID |
| `CI_PROJECT_NAME` | 8.10 | 0.5 | 当前正在构建的项目的目录名称. 例如，如果项目 URL 为`gitlab.example.com/group-name/project-1` ，则`CI_PROJECT_NAME`将为`project-1` . |
| `CI_PROJECT_NAMESPACE` | 8.10 | 0.5 | 当前正在构建的项目名称空间（用户名或组名） |
| `CI_PROJECT_ROOT_NAMESPACE` | 13.2 | 0.5 | 当前正在构建的**根**项目名称空间（用户名或组名）. 例如，如果`CI_PROJECT_NAME`是`root-group/child-group/grandchild-group` ，则`CI_PROJECT_ROOT_NAMESPACE`将是`root-group` . |
| `CI_PROJECT_PATH` | 8.10 | 0.5 | 具有项目名称的名称空间 |
| `CI_PROJECT_PATH_SLUG` | 9.3 | all | `$CI_PROJECT_PATH`小写，除`0-9`和`az`以外的所有内容都用`-`代替. 在 URL 和域名中使用. |
| `CI_PROJECT_REPOSITORY_LANGUAGES` | 12.3 | all | 库中使用的语言的逗号分隔，小写列表（例如`ruby,javascript,html,css` ） |
| `CI_PROJECT_TITLE` | 12.4 | all | 可读的项目名称，显示在 GitLab Web 界面中. |
| `CI_PROJECT_URL` | 8.10 | 0.5 | The HTTP(S) address to access project |
| `CI_PROJECT_VISIBILITY` | 10.3 | all | 项目可见性（内部，私人，公共） |
| `CI_REGISTRY` | 8.10 | 0.5 | 如果启用了 Container Registry，它将返回 GitLab 的 Container Registry 的地址. 如果在注册表配置中指定了一个变量，则该变量将包含`:port`值. |
| `CI_REGISTRY_IMAGE` | 8.10 | 0.5 | 如果为项目启用了容器注册表，则它将返回绑定到特定项目的注册表地址 |
| `CI_REGISTRY_PASSWORD` | 9.0 | all | The password to use to push containers to the GitLab Container Registry, for the current project. |
| `CI_REGISTRY_USER` | 9.0 | all | 用于将容器推送到当前项目的 GitLab 容器注册表的用户名. |
| `CI_REPOSITORY_URL` | 9.0 | all | 克隆 Git 存储库的 URL |
| `CI_RUNNER_DESCRIPTION` | 8.10 | 0.5 | 保存在 GitLab 中的跑步者的描述 |
| `CI_RUNNER_EXECUTABLE_ARCH` | all | 10.6 | GitLab Runner 可执行文件的操作系统/体系结构（请注意，它不一定与执行程序的环境相同） |
| `CI_RUNNER_ID` | 8.10 | 0.5 | 正在使用的跑步者的唯一 ID |
| `CI_RUNNER_REVISION` | all | 10.6 | 正在执行当前作业的 GitLab Runner 版本 |
| `CI_RUNNER_SHORT_TOKEN` | all | 12.3 | GitLab Runner 令牌的前八个字符用于验证新的作业请求. 用作跑步者的唯一 ID |
| `CI_RUNNER_TAGS` | 8.10 | 0.5 | 定义的运行器标签 |
| `CI_RUNNER_VERSION` | all | 10.6 | 正在执行当前作业的 GitLab Runner 版本 |
| `CI_SERVER` | all | all | 标记作业在 CI 环境中执行 |
| `CI_SERVER_URL` | 12.7 | all | GitLab 实例的基本 URL，包括协议和端口（例如`https://gitlab.example.com:8080` ） |
| `CI_SERVER_HOST` | 12.1 | all | GitLab 实例 URL 的主机组件，不带协议和端口（例如`gitlab.example.com` ） |
| `CI_SERVER_PORT` | 12.8 | all | GitLab 实例 URL 的端口组件，不包含主机和协议（例如`3000` ） |
| `CI_SERVER_PROTOCOL` | 12.8 | all | GitLab 实例 URL 的协议组件，不带主机和端口（例如`https` ） |
| `CI_SERVER_NAME` | all | all | 用于协调作业的 CI 服务器的名称 |
| `CI_SERVER_REVISION` | all | all | 用于计划作业的 GitLab 修订版 |
| `CI_SERVER_VERSION` | all | all | 用于计划作业的 GitLab 版本 |
| `CI_SERVER_VERSION_MAJOR` | 11.4 | all | GitLab 版本主要组件 |
| `CI_SERVER_VERSION_MINOR` | 11.4 | all | GitLab 版本次要组件 |
| `CI_SERVER_VERSION_PATCH` | 11.4 | all | GitLab 版本补丁组件 |
| `CI_SHARED_ENVIRONMENT` | all | 10.1 | 标记作业是在共享环境中执行的（在诸如`shell`或`ssh`执行程序之类的 CI 调用之间持久存在的内容）. 如果共享环境，则将其设置为 true，否则将完全未定义. |
| `GITLAB_CI` | all | all | 标记作业在 GitLab CI / CD 环境中执行 |
| `GITLAB_FEATURES` | 10.6 | all | 以逗号分隔的实例和计划可用的许可功能列表 |
| `GITLAB_USER_EMAIL` | 8.12 | all | 开始工作的用户的电子邮件 |
| `GITLAB_USER_ID` | 8.12 | all | 开始工作的用户的 ID |
| `GITLAB_USER_LOGIN` | 10.0 | all | 开始工作的用户的登录用户名 |
| `GITLAB_USER_NAME` | 10.0 | all | 开始工作的用户的真实姓名 |
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license