# Value Stream Analytics
> 原文：[https://docs.gitlab.com/ee/user/analytics/value_stream_analytics.html](https://docs.gitlab.com/ee/user/analytics/value_stream_analytics.html)
* [Overview](#overview)
* [Date ranges](#date-ranges)
* [How Time metrics are measured](#how-time-metrics-are-measured)
* [How the stages are measured](#how-the-stages-are-measured)
* [Example workflow](#example-workflow)
* [Customizable Value Stream Analytics](#customizable-value-stream-analytics)
* [Stage path](#stage-path)
* [Adding a stage](#adding-a-stage)
* [Re-ordering stages](#re-ordering-stages)
* [Label based stages](#label-based-stages)
* [Hiding unused stages](#hiding-unused-stages)
* [Days to completion chart](#days-to-completion-chart)
* [Chart median line](#chart-median-line)
* [Disabling chart](#disabling-chart)
* [Disabling chart median line](#disabling-chart-median-line)
* [Type of work - Tasks by type chart](#type-of-work---tasks-by-type-chart)
* [Permissions](#permissions)
* [More resources](#more-resources)
# Value Stream Analytics[](#value-stream-analytics "Permalink")
版本歷史
* 在項目級別在 GitLab 12.3 之前作為 Cycle Analytics 引入.
* 在小組級別的[GitLab Premium](https://about.gitlab.com/pricing/) 12.3 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/12077) .
* 在 GitLab 12.8 中從 Cycle Analytics [重命名](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/23427)為 Value Stream Analytics.
Value Stream Analytics measures the time spent to go from an [idea to production](https://about.gitlab.com/blog/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#from-idea-to-production-with-gitlab) (also known as cycle time) for each of your projects. Value Stream Analytics displays the median time spent in each stage defined in the process.
有關如何為 Value Stream Analytics 的發展做出貢獻的信息，請參閱我們的[貢獻者文檔](../../development/value_stream_analytics.html) .
值流分析有助于快速確定給定項目的速度. 它指出了開發過程中的瓶頸，從而使管理層能夠發現，分類和識別軟件開發生命周期中速度下降的根本原因.
Value Stream Analytics 與[GitLab 流程](../../topics/gitlab_flow.html)緊密結合，并為每個階段計算單獨的中位數.
## Overview[](#overview "Permalink")
價值流分析可用：
* 在 GitLab 12.9 中，通過**組>分析>值流**在組級別.
* 在項目級別，通過" **項目">"分析">"價值流"** .
作為"價值流分析"計算的一部分，將跟蹤七個階段.
* **Issue** (Tracker)
* 安排問題的時間（按里程碑或通過將其添加到問題板）
* **Plan** (Board)
* 第一次提交的時間
* **Code** (IDE)
* 是時候創建合并請求了
* **Test** (CI)
* GitLab CI / CD 測試代碼所需的時間
* **審核** （合并請求/ MR）
* 花在代碼審查上的時間
* **暫存** （連續部署）
* 合并和部署到生產之間的時間
* **Total** (Total)
* 總生命周期時間. 也就是說，項目或團隊的速度. [以前稱為](https://gitlab.com/gitlab-org/gitlab/-/issues/38317) **Production** .
## Date ranges[](#date-ranges "Permalink")
在 GitLab 12.4 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/13216) .
GitLab 提供了根據日期范圍過濾分析的功能. 要過濾結果：
1. 選擇一個組.
2. （可選）選擇一個項目.
3. 使用可用的日期選擇器選擇日期范圍.
## How Time metrics are measured[](#how-time-metrics-are-measured "Permalink")
頁面頂部附近的"時間"指標的測量方法如下：
* **提前期** ：從創建問題到關閉問題的平均時間.
* **周期時間** ：從第一次提交到發布完成的中值時間.
注意：通過在提交消息中進行[交聯](../project/issues/crosslinking_issues.html)或通過手動鏈接包含提交的合并請求，將提交與問題相關[聯](../project/issues/crosslinking_issues.html) .
[](img/vsa_time_metrics_v13_0.png)
## How the stages are measured[](#how-the-stages-are-measured "Permalink")
Value Stream Analytics 根據項目問題記錄階段時間和數據，但階段和總階段除外，在階段和總階段中，僅測量部署到生產中的數據.
具體而言，如果未設置 CI 且尚未定義`production`或`production/*` [環境](../../ci/yaml/README.html#environment) ，則此階段將沒有任何數據.
下表進一步描述了價值流分析的每個階段.
| **Stage** | **Description** |
| --- | --- |
| Issue | 通過標記問題或將其添加到里程碑中，以先發生的為準，來衡量從創建問題到采取行動解決問題之間的平均時間. 僅在標簽已經為其創建了[發行委員會列表的](../project/issue_board.html)情況下，才會跟蹤該標簽. |
| Plan | 測量您在上一階段采取的操作與將第一次提交推入分支之間的平均時間. 分支的第一個提交是觸發**計劃**和**代碼**之間分離的提交，并且分支中的至少一個提交需要包含相關的發行編號（例如`#42` ）. 如果分支中的所有提交都未提及相關的發行號，則不會考慮該階段的度量時間. |
| Code | 測量推入第一個提交（上一階段）與創建與該提交相關的合并請求（MR）之間的平均時間. 保持流程跟蹤的關鍵是在合并請求的描述中包括[問題關閉模式](../project/issues/managing_issues.html#closing-issues-automatically) （例如， `Closes #xxx` ，其中`xxx`是與此合并請求相關的問題編號）. 如果合并請求描述中不存在問題結束模式，則不會將 MR 視為平臺的測量時間. |
| Test | 測量運行該項目的整個管道的中值時間. 這與 GitLab CI / CD 為推送到上一階段中定義的合并請求的提交運行每個作業所花費的時間有關. 基本上，這是所有管道的開始->完成時間. |
| Review | 測量從創建到合并之間，審核具有結束問題模式的合并請求所需的平均時間. |
| Staging | 測量從合并合并請求到結束發布模式到首次部署到生產之間的平均時間. 在您的 GitLab CI / CD 配置中，通過設置為`production`或匹配`production/*` （區分大小寫， `Production`將不起作用）的環境進行跟蹤. 如果沒有生產環境，則不會進行跟蹤. |
| Total | 從問題創建到將代碼部署到生產中，運行整個過程所需的所有時間（中位數）之和. [以前稱為](https://gitlab.com/gitlab-org/gitlab/-/issues/38317) **Production** . |
幕后工作原理：
1. 問題和合并請求成對地分組在一起，這樣對于每個`<issue, merge request>`對，合并請求都具有對應問題的[問題關閉模式](../project/issues/managing_issues.html#closing-issues-automatically) . **不**考慮所有其他問題和合并請求.
2. 然后，在最近的 XX 天（由 UI 指定-默認為 90 天）中過濾出`<issue, merge request>`對. 因此，它禁止考慮這些對.
3. 對于其余的`<issue, merge request>`對，我們檢查階段所需的信息，例如發行日期，合并請求合并時間等.
綜上所述，不會跟蹤任何未遵循[GitLab 流程的](../../workflow/gitlab_flow.html)內容，并且 Value Stream Analytics 儀表板將不會顯示以下任何數據：
* 合并不會解決問題的請求.
* 未在發行委員會中貼有標簽的問題或未分配里程碑的問題.
* 如果項目沒有`production`或`production/*`環境，則為階段和生產階段.
## Example workflow[](#example-workflow "Permalink")
以下是一個簡單的虛擬周期工作流，它在一天中經歷了所有七個階段后，才發生. 請注意，如果一個階段沒有開始和結束標記，則不會對其進行測量，因此不會在中位時間中進行計算. 假定已創建里程碑并配置了用于測試和設置環境的 CI.
1. 在 09:00（ **發行**階段開始）創建**發行** .
2. 在 11:00（ **發行**階段停止/ **計劃**階段開始）將發行添加到里程碑.
3. 開始解決此問題，在本地創建一個分支，并在 12:00 提交一次.
4. 對分支進行第二次提交，該分支在 12.30（ **計劃**階段的停止/ **代碼**階段的開始）中提及發行號.
5. 推送分支并創建一個合并請求，該請求的描述在 14:00（ **代碼**階段停止/ **測試**和**復審**階段開始）中包含[問題關閉模式](../project/issues/managing_issues.html#closing-issues-automatically) .
6. CI 將開始運行您在[`.gitlab-ci.yml`](../../ci/yaml/README.html)定義的腳本，并需要 5 分鐘（ **測試**階段停止）.
7. 查看合并請求，確保一切正常，然后在 19:00 合并合并請求. （ **復習**階段的停止/啟動**分期**階段）.
8. 現在，合并請求合并，部署到`production`環境中開始和結束日 19:30（ **分期**階段停止）.
9. 循環完成，并且先前階段的中位數時間總和記錄到" **總計"**階段. 這是從創建問題到將其相關合并請求部署到生產之間的時間.
從上面的示例中，您可以得出每個階段完成所需的時間，只要達到其總時間即可：
* **問題** ：2 小時（11:00-09:00）
* **計劃** ：1 小時（12:00-11:00）
* **編碼** ：2h（14:00-12:00）
* **測試時間** ：5 分鐘
* **評論** ：5 小時（19:00-14:00）
* **演出時間** ：30 分鐘（19:30-19:00）
* **總計** ：由于此階段測量的是之前所有階段的中位時間之和，因此如果我們不知道之前各階段的狀態，則無法計算. 如果這是項目中運行的第一個周期，則**總**時間為 10h 30min（19:30-09:00）
一些注意事項：
* 在上面的示例中，我們演示了您的第一次提交沒有提到發行號也沒關系，您可以稍后在正在處理的分支的任何提交中進行此操作.
* 您可以看到，由于未將" **測試"**階段計算為整個周期的時間，因此" **檢查"**階段已包含在" **審查"**過程中（應測試每個 MR）.
* 上面的示例只是七個階段中的**一個循環** . 添加多個周期，計算它們的中值時間，結果就是 Value Stream Analytics 儀表板顯示的內容.
## Customizable Value Stream Analytics[](#customizable-value-stream-analytics "Permalink")
在 GitLab 12.9 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/12196) .
默認階段旨在直接使用，但是可能并不適合所有團隊. 不同的團隊使用不同的方法來構建軟件，因此一些團隊可能想要自定義其 Value Stream Analytics.
GitLab 允許用戶隱藏默認階段并創建自定義階段，使其更適合其開發工作流程.
**注意：**自定義性[僅適用于組級別的](https://gitlab.com/gitlab-org/gitlab/-/issues/35823#note_272558950)價值流分析.
### Stage path[](#stage-path "Permalink")
在 GitLab 13.0 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/210315) .
從視覺上將階段描繪為水平過程流. 選擇一個階段將更新值流下方的內容.
默認情況下禁用. 如果您具有自我管理的實例，則管理員可以[打開 Rails 控制臺](../../administration/troubleshooting/navigating_gitlab_via_rails_console.html)并使用以下命令啟用它：
```
Feature.enable(:value_stream_analytics_path_navigation)
```
### Adding a stage[](#adding-a-stage "Permalink")
在下面的示例中，我們將創建一個新階段，該階段可以衡量和跟蹤從創建到關閉的所有問題.
1. 導航到您組的" **分析">"價值流"** .
2. 單擊**添加階段**按鈕.
3. 填寫新的舞臺表格：
* 名稱：問題開始完成.
* 開始事件：已創建問題.
* 結束事件：問題已關閉.
4. 單擊**添加階段**按鈕.
[](img/new_vsm_stage_v12_9.png)
新階段將保持不變，并將始終顯示在您組的"價值流分析"頁面上.
如果要更改或刪除階段，可以通過以下方法輕松地針對自定義階段進行操作：
1. Hovering over the stage.
2. 單擊垂直省略號（ ）出現的按鈕.
[](img/vsm_stage_list_v12_9.png)
創建自定義階段需要指定兩個事件：
* 開始.
* 結束.
請小心選擇*在*結束事件*之前*發生的開始事件. 例如，考慮一個階段：
* 在將問題添加到板上時開始.
* 創建問題時結束.
此階段將不起作用，因為開始事件發生時，結束事件已經發生. 為防止此類無效階段，UI 禁止出現不兼容的開始和結束事件. 選擇開始事件后，停止事件下拉列表將僅列出兼容事件.
### Re-ordering stages[](#re-ordering-stages "Permalink")
在 GitLab 12.10 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/196698) .
添加自定義階段后，您可以"拖放"階段以重新排列其順序. 這些更改將自動保存到系統中.
### Label based stages[](#label-based-stages "Permalink")
預定義的開始和結束事件可以涵蓋涉及問題和合并請求的許多用例.
為了支持更復雜的工作流程，請使用基于組標簽的階段. 這些事件基于添加或刪除的標簽. 特別是， [范圍標簽](../project/labels.html#scoped-labels-premium)對于復雜的工作流程很有用.
在此示例中，我們希望測量更準確的代碼檢查時間. 工作流程如下：
* 代碼審閱開始時，審閱者將`workflow::code_review_start`標簽添加到合并請求中.
* 代碼檢查完成后，檢查者將`workflow::code_review_complete`標簽添加到合并請求中.
創建一個稱為"代碼審查"的新階段：
[](img/label_based_stage_vsm_v12_9.png)
### Hiding unused stages[](#hiding-unused-stages "Permalink")
有時某些默認階段與團隊無關. 在這種情況下，您可以輕松隱藏階段，使它們不再出現在列表中. 隱藏階段：
1. 添加定制階段以激活可定制性.
2. 將鼠標懸停在要隱藏的默認階段上.
3. 單擊垂直省略號（ ）按鈕出現，然后選擇" **隱藏舞臺"** .
要恢復以前隱藏的默認階段：
1. Click **添加一個階段** button.
2. 在右上角打開" **恢復隱藏的階段"**下拉列表.
3. 選擇一個階段.
## Days to completion chart[](#days-to-completion-chart "Permalink")
在 GitLab 12.6 中[引入](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/21631) .
該圖表直觀地描述了完成周期所需的總天數.
該圖表使用全局頁面過濾器來基于選定的組，項目和時間范圍顯示數據. 此外，可以從圖表本身內選擇特定階段.
### Chart median line[](#chart-median-line "Permalink")
在 GitLab 12.7 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/36675) .
圖表上的中間線顯示的數據偏移了所選的天數. 例如，如果選擇了 30 天的數據（例如 2019-12-16 至 2020-01-15），則中線將代表前 30 天的數據（2019-11-16 至 2019-12 -16）作為要比較的指標.
### Disabling chart[](#disabling-chart "Permalink")
This chart is enabled by default. If you have a self-managed instance, an administrator can open a Rails console and disable it with the following command:
```
Feature.disable(:cycle_analytics_scatterplot_enabled)
```
### Disabling chart median line[](#disabling-chart-median-line "Permalink")
默認情況下，此圖表的中線是啟用的. 如果您具有自我管理的實例，則管理員可以打開 Rails 控制臺并使用以下命令將其禁用：
```
Feature.disable(:cycle_analytics_scatterplot_median_enabled)
```
## Type of work - Tasks by type chart[](#type-of-work---tasks-by-type-chart "Permalink")
在 GitLab 12.10 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/32421) .
此圖表顯示每天的問題和合并請求的累積計數.
該圖表使用全局頁面過濾器來基于選定的組，項目和時間范圍顯示數據. 該圖表默認為顯示問題計數，但可以切換為顯示合并請求數據，并進一步細化為特定的組級標簽.
默認情況下，預先選擇了最高的組級別標簽（最多 10 個），最多可以選擇 15 個標簽.
## Permissions[](#permissions "Permalink")
Project Value Stream Analytics 儀表板上的當前權限為：
* 公共項目-任何人都可以訪問.
* 內部項目-任何經過身份驗證的用戶都可以訪問.
* 私人項目-訪客及以上的任何成員都可以訪問.
您通常可以[閱讀有關權限的更多信息](../../ci/yaml/README.html) .
對于 GitLab 12.3 和更高版本中引入的 Value Stream Analytics 功能：
* 用戶必須具有 Reporter 或更高權限.
* 僅在[Premium 或 Silver 等級](https://about.gitlab.com/pricing/)及更高[級別](https://about.gitlab.com/pricing/)上可用.
## More resources[](#more-resources "Permalink")
Learn more about Value Stream Analytics in the following resources:
* [Value Stream Analytics feature page](https://about.gitlab.com/stages-devops-lifecycle/value-stream-analytics/).
* [Value Stream Analytics feature preview](https://about.gitlab.com/blog/2016/09/16/feature-preview-introducing-cycle-analytics/).
* [Value Stream Analytics feature highlight](https://about.gitlab.com/blog/2016/09/21/cycle-analytics-feature-highlight/).
- 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