# GitLab Docs monthly release process
> 原文：[https://docs.gitlab.com/ee/development/documentation/site_architecture/release_process.html](https://docs.gitlab.com/ee/development/documentation/site_architecture/release_process.html)
* [How to build the images](#how-to-build-the-images)
* [Monthly release process](#monthly-release-process)
* [1\. Add the chart version](#1-add-the-chart-version)
* [2\. Create an image for a single version](#2-create-an-image-for-a-single-version)
* [3\. Create the release merge request](#3-create-the-release-merge-request)
* [4\. Update the dropdown for all online versions](#4-update-the-dropdown-for-all-online-versions)
* [5\. Merge the release merge request](#5-merge-the-release-merge-request)
* [Update an old Docker image with new upstream docs content](#update-an-old-docker-image-with-new-upstream-docs-content)
* [Porting new website changes to old versions](#porting-new-website-changes-to-old-versions)
* [Troubleshooting](#troubleshooting)
* [`test_internal_links_and_anchors` failing on dropdown merge requests](#test_internal_links_and_anchors-failing-on-dropdown-merge-requests)
# GitLab Docs monthly release process[](#gitlab-docs-monthly-release-process "Permalink")
[`dockerfiles`目录](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/dockerfiles/)包含构建和部署版本控制网站所需的所有 Dockerfile. 它在很大程度上受到了 Docker 的[Dockerfile 的](https://github.com/docker/docker.github.io/blob/06ed03db13895bfe867761b6fc2ad40acf6026dd/Dockerfile)启发.
使用以下 Dockerfile.
| Dockerfile | Docker 镜像 | Description |
| --- | --- | --- |
| [`Dockerfile.bootstrap`](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/dockerfiles/Dockerfile.bootstrap) | `gitlab-docs:bootstrap` | 包含构建网站所需的所有依赖项. 如果宝石已更新且`Gemfile{,.lock}`更改，则必须重建映像. |
| [`Dockerfile.builder.onbuild`](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/dockerfiles/Dockerfile.builder.onbuild) | `gitlab-docs:builder-onbuild` | 用于建立 docs 网站的基本图片. 它使用`ONBUILD`执行所有步骤，并取决于`gitlab-docs:bootstrap` . |
| [`Dockerfile.nginx.onbuild`](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/dockerfiles/Dockerfile.nginx.onbuild) | `gitlab-docs:nginx-onbuild` | 用于构建文档档案的基本映像. 它使用`ONBUILD`执行所有必需的步骤来复制档案，并依赖于其父`Dockerfile.builder.onbuild` ，该父文件在构建单个文档档案时被调用（请参阅每个分支的`Dockerfile` . |
| [`Dockerfile.archives`](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/dockerfiles/Dockerfile.archives) | `gitlab-docs:archives` | 在一个档案中包含网站的所有版本. 它从一个位置中的每个版本复制所有生成的 HTML 文件. |
## How to build the images[](#how-to-build-the-images "Permalink")
尽管构建映像是通过 GitLab CI / CD 自动构建的，但是您可以在本地构建和标记所有工具映像：
1. 确保已[安装 Docker](https://s0docs0docker0com.icopy.site/install/) .
2. 确保您位于`gitlab-docs`存储库的`dockerfiles/`目录中.
3. 构建图像：
```
docker build -t registry.gitlab.com/gitlab-org/gitlab-docs:bootstrap -f Dockerfile.bootstrap ../
docker build -t registry.gitlab.com/gitlab-org/gitlab-docs:builder-onbuild -f Dockerfile.builder.onbuild ../
docker build -t registry.gitlab.com/gitlab-org/gitlab-docs:nginx-onbuild -f Dockerfile.nginx.onbuild ../
```
对于每个图像， [`.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab-docs/blob/master/.gitlab-ci.yml)的`images`阶段下都有一个手动作业，可以随意调用.
## Monthly release process[](#monthly-release-process "Permalink")
当 22 日发布新版本的 GitLab 时，我们需要创建相应的单个 Docker 映像，并更新一些文件，以使下拉列表正常工作.
### 1\. Add the chart version[](#1-add-the-chart-version "Permalink")
由于图表使用的版本号不同于所有其他 GitLab 产品，因此我们需要添加一个[版本映射](https://docs.gitlab.com/charts/installation/version_mappings.html) ：
1. 检查是否为新的图表版本[创建](https://gitlab.com/gitlab-org/charts/gitlab/-/branches)了[稳定的分支](https://gitlab.com/gitlab-org/charts/gitlab/-/branches) . 如果不确定或找不到，请在`#g_delivery`频道中添加一行.
2. 确保您位于`gitlab-docs`存储库的根路径中.
3. 打开`content/_data/chart_versions.yaml`并使用版本映射添加新的稳定分支版本. 请注意，仅需要`major.minor`版本.
4. 创建一个新的合并请求并将其合并.
**提示：**创建将来的映射可能很方便，因为它们已广为人知. 在这种情况下，当发布新版本的 GitLab 时，您不必重复此第一步.
### 2\. Create an image for a single version[](#2-create-an-image-for-a-single-version "Permalink")
必须在发布合并请求之前创建单个 docs 版本，但这需要在为所有产品创建稳定分支之后发生.
1. 确保您位于`gitlab-docs`存储库的根路径中.
2. 运行 Rake 任务以创建单个版本：
```
./bin/rake "release:single[12.0]"
```
应该已经创建了新的`Dockerfile.12.0`并且`.gitlab-ci.yml`应该将分支变量更新为新的分支. 他们将被自动提交.
3. 推送新创建的分支，但**不要创建合并请求** . 推送后， `image:docker-singe`作业将创建一个新的 Docker 映像，该映像标记有您在第一步中创建的分支名称. 最后，该图像将被上载到[Container Registry 中](https://gitlab.com/gitlab-org/gitlab-docs/container_registry) ，并且将在位于`https://gitlab.com/gitlab-org/gitlab-docs/-/environments/folders/registry`的`registry`环境文件夹下列出.开发人员访问权限）.
（可选）您可以通过构建映像并运行它来进行本地测试：
```
docker build -t docs:12.0 -f Dockerfile.12.0 .
docker run -it --rm -p 4000:4000 docs:12.0
```
访问`http://localhost:4000/12.0/`以查看一切是否正常.
### 3\. Create the release merge request[](#3-create-the-release-merge-request "Permalink")
**Note:** To be [automated](https://gitlab.com/gitlab-org/gitlab-docs/-/issues/750).
现在是时候创建每月发布合并请求，添加新版本并轮换旧版本了：
1. 确保您位于`gitlab-docs`存储库的根路径中.
2. 创建一个分支`release-XY` ：
```
git checkout master
git checkout -b release-12-0
```
3. **轮换在线和离线版本：**
在任何给定时间，都有 4 个可浏览的在线版本：一个是从上游主分支（GitLab.com 的文档）中提取的，另一个是三个最新的稳定版本.
编辑`content/_data/versions.yaml`并旋转版本以反映新的更改：
* `online` ：3 个最新的稳定版本.
* `offline` ：所有以前的版本都以脱机存档的形式提供.
4. **更新`:latest`和`:archives` Docker 映像：**
需要更新以下两个 Dockerfile：
1. `dockerfiles/Dockerfile.archives`在列表顶部添加最新版本.
2. `Dockerfile.master`旋转版本（最旧的被删除，最新的被添加在列表的顶部）.
5. 最后，应该总共更改了四个文件. 提交并使用"发布"模板推送以创建合并请求：
```
git add content/ Dockerfile.master dockerfiles/Dockerfile.archives
git commit -m "Release 12.0"
git push origin release-12-0
```
### 4\. Update the dropdown for all online versions[](#4-update-the-dropdown-for-all-online-versions "Permalink")
版本下拉列表采用"硬编码"方式. 在构建站点时，它将查看`content/_data/versions.yaml`的内容，并基于此内容填充下拉列表. 因此，较旧的分支将具有不同的内容，这意味着下拉列表将在后面列出一个或多个版本. 请记住，下拉菜单的新更改包含在未合并的`release-XY`分支中.
The content of `content/_data/versions.yaml` needs to change for all online versions:
1. 运行 Rake 任务，该任务将创建更新下拉列表所需的所有各个合并请求，并将其设置为在管道成功后自动合并. `release-XY`分支需要在本地存在，并且您需要切换到该分支，否则 Rake 任务将失败：
```
./bin/rake release:dropdowns
```
2. [访问合并请求页面](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests?label_name[]=release)以检查其管道是否通过，并在所有管道合并后继续进行以下也是最后一步.
**提示：**万一管道发生故障，请参阅[故障排除](#troubleshooting) .
### 5\. Merge the release merge request[](#5-merge-the-release-merge-request "Permalink")
下拉合并请求现在应该已经合并到各自的版本（稳定分支）中，这将触发另一个管道. 在这一点上，您只需要照看管道，并确保它们不会失败：
1. 检查管道页面： `https://gitlab.com/gitlab-org/gitlab-docs/pipelines` : `https://gitlab.com/gitlab-org/gitlab-docs/pipelines`并确保所有稳定的分支都具有绿色管道.
2. 联机版本的所有管道成功后，请合并发布合并请求.
3. 最后，从`https://gitlab.com/gitlab-org/gitlab-docs/pipeline_schedules`运行`Build docker images weekly` Docker 映像管道，以构建`:latest`和`:archives` Docker 映像.
一旦计划的管道成功，将在线部署所有新版本的 docs 网站.
## Update an old Docker image with new upstream docs content[](#update-an-old-docker-image-with-new-upstream-docs-content "Permalink")
如果对单个 Docker 映像中未包含的产品的任何稳定分支进行了任何更改，只需重新运行管道（ `https://gitlab.com/gitlab-org/gitlab-docs/pipelines/new` ）有问题的版本.
## Porting new website changes to old versions[](#porting-new-website-changes-to-old-versions "Permalink")
**警告：将**更改移植到较旧的分支机构可能会产生意想不到的影响，因为我们不断更改网站的后端. 仅在知道自己在做什么并确保在本地进行测试时使用.
网站将不断变化和完善. 为了将这些更改合并到稳定分支中，我们需要不时选择某些更改.
如果这不可能或有很多更改，请将 master 合并到其中：
```
git branch 12.0
git fetch origin master
git merge origin/master
```
## Troubleshooting[](#troubleshooting "Permalink")
发布新版本是一个漫长的过程，涉及许多活动部件.
### `test_internal_links_and_anchors` failing on dropdown merge requests[](#test_internal_links_and_anchors-failing-on-dropdown-merge-requests "Permalink")
**注意：**我们现在将版本`.gitlab-ci.yml`在相应分支的`.gitlab-ci.yml`中，因此不建议使用以下步骤.
当[更新稳定版本的下拉列表时](#4-update-the-dropdown-for-all-online-versions) ，某些链接可能会失败. 创建下拉式 MR 的过程有一个警告，那就是通过拉动所有产品的主分支而不是相应的稳定分支来运行测试.
在实际情况下，由于[`test_internal_links_and_anchors` test](https://gitlab.com/gitlab-org/gitlab-docs/-/jobs/328042431) [，导致与 12.4](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/604)合并请求[相匹配](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/604)的[Update 12.2 下拉列表](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/604)失败.
发生这种情况是因为已经对产品进行了重命名（ `gitlab-monitor`到`gitlab-exporter` ），而旧名称仍在 12.2 文档中引用. 如果使用了 12.2 的各个稳定分支，则不会失败，但是从[`compile_dev`作业中](https://gitlab.com/gitlab-org/gitlab-docs/-/jobs/328042427)可以看出， `master`分支已被拉出.
要解决此问题， `https://gitlab.com/gitlab-org/gitlab-docs/pipelines/new`为`update-12-2-for-release-12-4`分支重新运行管道（ `https://gitlab.com/gitlab-org/gitlab-docs/pipelines/new` ），以下环境变量：
* `BRANCH_CE`设置为`12-2-stable`
* `BRANCH_EE`设置为`12-2-stable-ee`
* `BRANCH_OMNIBUS`设置为`12-2-stable`
* `BRANCH_RUNNER`设置为`12-2-stable`
* `BRANCH_CHARTS`设置为`2-2-stable`
这应该使 MR 通过.
- 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