# Continuous Integration and Deployment Admin settings
> 原文:[https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html)
* [Auto DevOps](#auto-devops-core-only)
* [Maximum artifacts size](#maximum-artifacts-size-core-only)
* [Default artifacts expiration](#default-artifacts-expiration-core-only)
* [Shared Runners pipeline minutes quota](#shared-runners-pipeline-minutes-quota-starter-only)
* [Archive jobs](#archive-jobs-core-only)
* [Default CI configuration path](#default-ci-configuration-path)
* [Required pipeline configuration](#required-pipeline-configuration-premium-only)
* [Package Registry configuration](#package-registry-configuration-premium-only)
# Continuous Integration and Deployment Admin settings[](#continuous-integration-and-deployment-admin-settings-core-only "Permalink")
在此區域中,您將找到 Auto DevOps,Runners 和作業工件的設置. 您可以在**管理區域>設置> CI / CD 中**找到它.
[](../img/admin_area_settings_button.png)
## Auto DevOps[](#auto-devops-core-only "Permalink")
要為所有項目啟用(或禁用) [Auto DevOps](../../../topics/autodevops/index.html) :
1. 轉到**管理區域>設置> CI / CD** .
2. 選中(或取消選中以禁用) **所有項目的默認為 Auto DevOps 管道**的框.
3. (可選)設置將用于 Auto Deploy 和 Auto Review Apps 的[Auto DevOps 基本域](../../../topics/autodevops/index.html#auto-devops-base-domain) .
4. 點擊**保存更改**以使更改生效.
從現在開始,每個不帶`.gitlab-ci.yml`現有項目和新創建的項目都將使用 Auto DevOps 管道.
如果要為特定項目禁用它,可以在[其設置中](../../../topics/autodevops/index.html#enablingdisabling-auto-devops)禁用它.
## Maximum artifacts size[](#maximum-artifacts-size-core-only "Permalink")
可以將[作業工件](../../../administration/job_artifacts.html)的最大大小設置為:
* 實例級別.
* [從 GitLab 12.4 開始](https://gitlab.com/gitlab-org/gitlab/-/issues/21688) ,為項目和組級別.
值是:
* 以*MB*為單位,每個作業的默認值為 100MB.
* 在 GitLab.com 上[設置為 1G](../../gitlab_com/index.html#gitlab-cicd) .
要在以下位置進行更改:
* 實例級別:
1. Go to **管理區域>設置> CI / CD**.
2. 更改最大工件大小的值(以 MB 為單位).
3. 單擊**保存更改**以使更改生效.
* [組級別](../../group/index.html#group-settings) (這將覆蓋實例設置):
1. 轉到組的**設置> CI / CD>常規管道** .
2. 更改**最大工件大小**的值**(以 MB 為單位)** .
3. 單擊**保存更改**以使更改生效.
* [項目級別](../../../ci/pipelines/settings.html) (這將覆蓋實例和組設置):
1. 轉到項目的**設置> CI / CD>常規管道** .
2. 更改**最大工件大小**的值**(以 MB 為單位)** .
3. 單擊**保存更改**以使更改生效.
**注意:**所有級別的設置僅對 GitLab 管理員可用.
## Default artifacts expiration[](#default-artifacts-expiration-core-only "Permalink")
可以在 GitLab 實例的"管理區域"中設置[作業工件](../../../administration/job_artifacts.html)的默認過期時間. 持續時間的語法在[`artifacts:expire_in`](../../../ci/yaml/README.html#artifactsexpire_in)描述,缺省值為`30 days` .
1. 轉到**管理區域>設置> CI / CD** .
2. 更改默認到期時間的值.
3. 單擊**保存更改**以使更改生效.
此設置是[`.gitlab-ci.yml`](../../../ci/yaml/README.html#artifactsexpire_in)每個作業設置的,可以在[`.gitlab-ci.yml`](../../../ci/yaml/README.html#artifactsexpire_in)覆蓋. 要禁用到期時間,請將其設置為`0` . 默認單位是秒.
**注意:**對此設置的任何更改將僅適用于新工件. 更改此設置之前創建的工件的過期時間將不會更新. 管理員可能需要手動搜索并終止先前創建的工件,如[故障排除文檔中所述](../../../administration/troubleshooting/gitlab_rails_cheat_sheet.html#remove-artifacts-more-than-a-week-old) .
## Shared Runners pipeline minutes quota[](#shared-runners-pipeline-minutes-quota-starter-only "Permalink")
在 GitLab Starter 8.16 中[引入](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1078) .
如果已為 GitLab 實例啟用共享運行程序,則可以通過設置組每月可以在共享運行程序上使用的最大管道分鐘數來限制其使用. 將此設置為`0` (默認值)將授予無限制的管道分鐘數. 盡管構建限制以分鐘存儲,但計數以秒為單位. 使用情況會在每個月的第一天重置. 在 GitLab.com 上,配額是根據您的[訂閱計劃](https://about.gitlab.com/pricing/#gitlab-com)計算的.
要更改管道分鐘配額:
1. 轉到**管理區域>設置> CI / CD** .
2. Expand **持續集成和部署**.
3. 在" **管道分鐘數"配額**框中,輸入最大分鐘數.
4. 單擊**保存更改**以使更改生效.
* * *
盡管"管理區域"中的設置具有全局作用,但作為管理員,您也可以更改每個組的管道分鐘配額以覆蓋全局值.
1. 導航到" **管理區域">"概述">"組",**然后單擊您要更改管道分鐘配額的組的" **編輯"**按鈕.
2. 在" **管道分鐘配額"**框中,輸入最大分鐘數.
3. 單擊**保存更改**以使更改生效.
保存后,您可以在組管理員視圖中查看構建配額. 如果啟用了共享運行器,也可以在項目管理視圖中查看配額.
[](img/admin_project_quota_view.png)
您可以在組頁面設置列表可用的" **使用配額"**頁面中查看該組所有項目的管道分鐘配額的概述.
[](img/group_pipelines_quota.png)
## Archive jobs[](#archive-jobs-core-only "Permalink")
歸檔作業通過刪除作業的某些功能(運行作業所需的元數據)來減少系統上的 CI / CD 占用空間,但保留跡線和工件以供審核時很有用.
設置作業將被視為過期和過期的持續時間:
1. 轉到**管理區域>設置> CI / CD** .
2. 展開**持續集成和部署**部分.
3. 設置**存檔作業**的值.
4. 點擊**保存更改**以使更改生效.
一旦超過該時間,作業將被存檔,并且不再能夠重試. 將其設為空以永不過期作業. 它必須不少于 1 天,例如: `15 days` , `1 month` , `2 years` .
截至 2020 年 6 月 22 日,該[值](../../gitlab_com/index.html#gitlab-cicd)在 GitLab.com 上[設置](../../gitlab_com/index.html#gitlab-cicd)為 3 個月. 在此日期之前創建的作業將在 2020 年 9 月 22 日之后存檔.
## Default CI configuration path[](#default-ci-configuration-path "Permalink")
在 GitLab 12.5 中[引入](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/18073) .
可以在您的 GitLab 實例的"管理"區域中設置新項目的默認 CI 配置文件路徑(如果未設置, `.gitlab-ci.yml` ):
1. 轉到**管理區域>設置> CI / CD** .
2. 在**默認 CI 配置路徑**字段中輸入新路徑.
3. 點擊**保存更改**以使更改生效.
也可以[為特定項目](../../../ci/pipelines/settings.html#custom-ci-configuration-path)指定[自定義 CI 配置路徑](../../../ci/pipelines/settings.html#custom-ci-configuration-path) .
## Required pipeline configuration[](#required-pipeline-configuration-premium-only "Permalink")
**警告:**此功能正在重新評估,以支持其他[合規性解決方案](https://gitlab.com/gitlab-org/gitlab/-/issues/34830) . 我們建議尚未實施此功能的用戶等待新解決方案.
GitLab 管理員可以強制管道配置在每個管道上運行.
該配置適用于 GitLab 實例的所有管道,其來源為:
* The [instance template repository](instance_template_repository.html).
* GitLab 提供的配置.
設置所需的管道配置:
1. 轉到**管理區域>設置> CI / CD** .
2. 展開" **所需管道配置"**部分.
3. 從提供的下拉列表中選擇所需的配置.
4. Click **保存更改**.
[](img/admin_required_pipeline.png)
## Package Registry configuration[](#package-registry-configuration-premium-only "Permalink")
GitLab 管理員可以禁用將 NPM 請求轉發到[npmjs.com](https://s0www0npmjs0com.icopy.site/) .
To disable it:
1. 轉到**管理區域>設置> CI / CD** .
2. 展開" **程序包注冊表"**部分.
3. Uncheck **啟用將 NPM 軟件包請求轉發到 npmjs.org**.
4. Click **保存更改**.
[](img/admin_package_registry_npm_package_requests_forward.png)
- 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