# GitLab CI/CD
> 原文：[https://docs.gitlab.com/ee/ci/README.html](https://docs.gitlab.com/ee/ci/README.html)
* [Overview](#overview)
* [Getting started](#getting-started)
* [Concepts](#concepts)
* [Configuration](#configuration)
* [Feature set](#feature-set)
* [Examples](#examples)
* [Administration](#administration-core-only)
* [References](#references)
* [Why GitLab CI/CD?](#why-gitlab-cicd)
* [Breaking changes](#breaking-changes)
* [13.0](#130)
* [12.0](#120)
* [11.0](#110)
* [10.0](#100)
* [9.0](#90)
# GitLab CI/CD[](#gitlab-cicd "Permalink")
GitLab CI / CD 是 GitLab 內置的工具，用于通過[連續方法](introduction/index.html#introduction-to-cicd-methodologies)進行軟件開發：
* 持續集成（CI）
* 連續交付（CD）
* 持續部署（CD）
**注意：**開箱即用的管理系統可以將維護工具鏈所花費的時間減少 10％或更多. 觀看我們的["精通持續軟件開發"](https://about.gitlab.com/webcast/mastering-ci-cd/)網絡廣播，以了解連續方法以及 GitLab 的內置 CI 如何幫助您簡化和擴展軟件開發.
## Overview[](#overview "Permalink")
持續集成的工作原理是將小的代碼塊推送到 Git 存儲庫中托管的應用程序代碼庫中，并且每次推送時，都要運行腳本管道來構建，測試和驗證代碼更改，然后再將其合并到主分支中.
持續交付和部署包括進一步的 CI，可在每次推送到存儲庫默認分支時將應用程序部署到生產環境.
這些方法使您可以在開發周期的早期發現錯誤和錯誤，從而確保部署到生產環境的所有代碼均符合為應用程序建立的代碼標準.
有關這些方法和 GitLab CI / CD 的完整概述，請閱讀 GitLab 的 CI / CD [簡介](introduction/index.html) .
GitLab CI / CD 的視頻演示： [演示：](https://www.youtube.com/watch?v=1iXFbchozdY) GitLab 的 CI / CD.
<figure class="video-container"><iframe src="https://www.youtube.com/embed/1iXFbchozdY" frameborder="0" allowfullscreen=""></iframe></figure>
## Getting started[](#getting-started "Permalink")
GitLab CI / CD 由位于存儲庫根目錄的名為`.gitlab-ci.yml`的文件配置. 該文件創建[管道](pipelines/index.html) ，該[管道](pipelines/index.html)運行以更改存儲庫中的代碼. 管道包含一個或多個順序運行的階段，每個階段可以包含一個或多個并行運行的作業. 這些作業（或腳本）由[GitLab Runner](https://docs.gitlab.com/runner/)代理執行.
要開始使用 GitLab CI / CD，我們建議您通讀以下文檔：
* [How GitLab CI/CD works](introduction/index.html#how-gitlab-cicd-works).
* [Fundamental pipeline architectures](pipelines/pipeline_architectures.html).
* [GitLab CI/CD basic workflow](introduction/index.html#basic-cicd-workflow).
* [Step-by-step guide for writing `.gitlab-ci.yml` for the first time](../user/project/pages/getting_started/pages_from_scratch.html).
如果您要從其他 CI / CD 工具遷移，請查看我們方便的參考資料：
* [Migrating from CircleCI](migration/circleci.html)
* [Migrating from Jenkins](jenkins/index.html)
您也可以使用 UI 中提供的[`.gitlab-ci.yml`模板](https://gitlab.com/gitlab-org/gitlab-foss/tree/master/lib/gitlab/ci/templates)之一來開始使用. 您可以通過創建新文件，選擇適合您的應用程序的模板并根據需要進行調整來使用它們：
[](img/add_file_template_11_10.png)
有關更廣泛的概述，請參閱《 [CI / CD 入門](quick_start/README.html)指南》.
熟悉 GitLab CI / CD 的工作原理后，請參閱[`.gitlab-ci.yml`完整參考，](yaml/README.html)以獲取可以設置和使用的所有屬性.
**注意：** GitLab CI / CD 和[共享運行](runners/README.html#shared-runners)器在 GitLab.com 中啟用，并且對所有用戶可用，僅限于[用戶的管道配額](../user/gitlab_com/index.html#shared-runners) .
## Concepts[](#concepts "Permalink")
GitLab CI / CD 使用許多概念來描述和運行您的構建和部署.
| Concept | Description |
| --- | --- |
| [Pipelines](pipelines/index.html) | Structure your CI/CD process through pipelines. |
| [Environment variables](variables/README.html) | 根據變量/值鍵對重用值. |
| [Environments](environments/index.html) | 將您的應用程序部署到不同的環境（例如，登臺，生產）. |
| [Job artifacts](pipelines/job_artifacts.html) | 輸出，使用和重用作業工件. |
| [Cache dependencies](caching/index.html) | 緩存您的依賴項以加快執行速度. |
| [GitLab Runner](https://docs.gitlab.com/runner/) | 配置自己的 GitLab 運行程序以執行腳本. |
## Configuration[](#configuration "Permalink")
GitLab CI / CD 支持多種配置選項：
| Configuration | Description |
| --- | --- |
| [Schedule pipelines](pipelines/schedules.html) | 計劃管道以根據需要運行. |
| [Custom path for `.gitlab-ci.yml`](pipelines/settings.html#custom-ci-configuration-path) | 為 CI / CD 配置文件定義自定義路徑. |
| [Git submodules for CI/CD](git_submodules.html) | 配置作業以使用 Git 子模塊. |
| [SSH keys for CI/CD](ssh_keys/README.html) | 在 CI 管道中使用 SSH 密鑰. |
| [Pipeline triggers](triggers/README.html) | 通過 API 觸發管道. |
| [Pipelines for Merge Requests](merge_request_pipelines/index.html) | 設計用于在合并請求中運行管道的管道結構. |
| [Integrate with Kubernetes clusters](../user/project/clusters/index.html) | 將您的項目連接到 Google Kubernetes Engine（GKE）或現有的 Kubernetes 集群. |
| [Optimize GitLab and Runner for large repositories](large_repositories/index.html) | 處理大型存儲庫的推薦策略. |
| [`.gitlab-ci.yml` full reference](yaml/README.html) | 您可以在 GitLab CI / CD 中使用的所有屬性. |
請注意，某些操作只能根據[用戶](../user/permissions.html#gitlab-cicd-permissions)和[作業](../user/permissions.html#job-permissions)權限執行.
## Feature set[](#feature-set "Permalink")
使用龐大的 GitLab CI / CD 可以輕松地針對特定目的進行配置. 根據 DevOps 階段，其功能集在下表中列出.
| Feature | Description |
| --- | --- |
| **Configure** | ? |
| [Auto DevOps](../topics/autodevops/index.html) | 設置應用的整個生命周期. |
| [ChatOps](chatops/README.html) | 從聊天中觸發 CI 作業，并將結果發送回通道. |
| **Verify** | ? |
| [Browser Performance Testing](../user/project/merge_requests/browser_performance_testing.html) | 快速確定即將發生的代碼更改對瀏覽器性能的影響. |
| [Load Performance Testing](../user/project/merge_requests/load_performance_testing.html) | 快速確定未決代碼更改對服務器性能的影響. |
| [CI services](services/README.html) | 將 Docker 容器與您的基本映像鏈接起來. |
| [Code Quality](../user/project/merge_requests/code_quality.html) | 分析您的源代碼質量. |
| [GitLab CI/CD for external repositories](ci_cd_for_external_repos/index.html) | 結合使用 GitHub 和 Bitbucket Cloud 中的存儲庫，獲得 GitLab CI / CD 的優勢. |
| [Interactive Web Terminals](interactive_web_terminal/index.html) | 打開一個交互式 Web 終端以調試正在運行的作業. |
| [JUnit tests](junit_test_reports.html) | 直接在合并請求中識別腳本失敗. |
| [Using Docker images](docker/using_docker_images.html) | 將 GitLab 和 GitLab Runner 與 Docker 結合使用來構建和測試應用程序. |
| **Release** | ? |
| [Auto Deploy](../topics/autodevops/stages.html#auto-deploy) | 將您的應用程序部署到 Kubernetes 集群中的生產環境. |
| [Building Docker images](docker/using_docker_build.html) | 使用 GitLab CI / CD 維護基于 Docker 的項目. |
| [Canary Deployments](../user/project/canary_deployments.html) | 僅將功能部件運送到一部分吊艙中，并讓一定比例的用戶群訪問臨時部署的功能部件. |
| [Deploy Boards](../user/project/deploy_boards.html) | 檢查 Kubernetes 上運行的每個 CI / CD 環境的當前運行狀況和狀態. |
| [Feature Flags](../operations/feature_flags.html) | 在功能標記后部署功能. |
| [GitLab Pages](../user/project/pages/index.html) | 部署靜態網站. |
| [GitLab Releases](../user/project/releases/index.html) | 將發行說明添加到 Git 標簽. |
| [Review Apps](review_apps/index.html) | 配置 GitLab CI / CD 預覽代碼更改. |
| [Cloud deployment](cloud_deployment/index.html) | 將您的應用程序部署到主要的云提供商. |
| **Secure** | ? |
| [Container Scanning](../user/application_security/container_scanning/index.html) | 檢查您的 Docker 容器是否存在已知漏洞. |
| [Dependency Scanning](../user/application_security/dependency_scanning/index.html) | 分析您的依賴項是否存在已知漏洞. |
| [License Compliance](../user/compliance/license_compliance/index.html) | 在項目依賴項中搜索其許可證. |
| [Security Test reports](../user/application_security/index.html) | 檢查應用程序漏洞. |
## Examples[](#examples "Permalink")
在" [CI 實例"](examples/README.html)頁面上查找示例項目代碼和教程，以將 GitLab CI / CD 與各種應用程序框架，語言和平臺結合使用.
GitLab 還提供了[示例項目，這些項目已](https://gitlab.com/gitlab-examples)預先配置為使用 GitLab CI / CD.
## Administration[](#administration-core-only "Permalink")
作為 GitLab 管理員，您可以將 GitLab CI / CD 的默認行為更改為：
* An [entire GitLab instance](../user/admin_area/settings/continuous_integration.html).
* 具體項目，使用[管道設置](pipelines/settings.html) .
也可以看看：
* [How to enable or disable GitLab CI/CD](enable_or_disable_ci.html).
* Other [CI administration settings](../administration/index.html#continuous-integration-settings).
## References[](#references "Permalink")
### Why GitLab CI/CD?[](#why-gitlab-cicd "Permalink")
學習更多關于：
* [Why you might chose GitLab CI/CD](https://about.gitlab.com/blog/2016/10/17/gitlab-ci-oohlala/).
* [Reasons you might migrate from another platform](https://about.gitlab.com/blog/2016/07/22/building-our-web-app-on-gitlab-ci/).
* [5 Teams that made the switch to GitLab CI/CD](https://about.gitlab.com/blog/2019/04/25/5-teams-that-made-the-switch-to-gitlab-ci-cd/)
另請參閱[為什么選擇 CI / CD？](https://docs.google.com/presentation/d/1OGgk2Tcxbpl7DJaIOzCX4Vqg3dlwfELC3u2jEeCBbDk) 介紹.
### Breaking changes[](#breaking-changes "Permalink")
隨著 GitLab CI / CD 的發展，必須進行一些重大更改. 這些是：
#### 13.0[](#130 "Permalink")
* [Remove Backported `os.Expand`](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4915)
* [Remove Fedora 29 package support](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/16158)
* [Remove macOS 32-bit support](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/25466)
* [Removed `debug/jobs/list?v=1` endpoint](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6361)
* [Remove support for array of strings when defining services for Docker executor](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4922)
* [Remove `--docker-services` flag on register command](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6404)
* [Remove legacy build directory caching](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4180)
* [Remove `FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER` feature flag](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6581)
* [Remove support for Windows Server 1803](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6553)
#### 12.0[](#120 "Permalink")
* [Use refspec to clone/fetch Git repository](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4069).
* [Old cache configuration](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4070).
* [Old metrics server configuration](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4072).
* [Remove `FF_K8S_USE_ENTRYPOINT_OVER_COMMAND`](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4073).
* [Remove Linux distributions that reach EOL](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/1130).
* [Update command line API for helper images](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4013).
* [Remove old `git clean` flow](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4175).
#### 11.0[](#110 "Permalink")
* 沒有重大變化.
#### 10.0[](#100 "Permalink")
* 沒有重大變化.
#### 9.0[](#90 "Permalink")
* [為 GitLab 9.0 重命名 CI 變量](variables/deprecated_variables.html#gitlab-90-renamed-variables) . 了解不建議使用的 CI 變量以及在 GitLab 9.0+中應使用的內容.
* [新的 CI 作業權限模型](../user/project/new_ci_build_permissions_model.html) . 查看 GitLab 8.12 中的更改及其對工作的影響. 有一種新方法可以訪問作業中的 Git 子模塊和 LFS 對象.
- 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