Skip to content
Snippets Groups Projects
Verified Commit e820ac73 authored by Suzanne Selhorn's avatar Suzanne Selhorn Committed by GitLab
Browse files

Updating tier badge format

Because for now, we're changing the format.

Related to: gitlab-docs#1751
parent b819a6aa
No related branches found
No related tags found
2 merge requests!144312Change service start (cut-off) date for code suggestions to March 15th,!142611Updating tier badge format
Showing
with 123 additions and 43 deletions
......@@ -258,7 +258,11 @@ production, GitLab creates a `production_manual` job.
You can also enable manual deployment in your [project settings](requirements.md#auto-devops-deployment-strategy).
## Deploy policy for canary environments **(PREMIUM ALL)**
## Deploy policy for canary environments
DETAILS:
**Tier:** Premium, Ultimate
**Offering:** SaaS, self-managed
You can use a [canary environment](../../user/project/canary_deployments.md) before
deploying any changes to production.
......@@ -268,7 +272,11 @@ If you set `CANARY_ENABLED`, GitLab creates two [manual jobs](../../ci/pipelines
- `canary` - Deploys the application to the canary environment.
- `production_manual` - Deploys the application to production.
## Incremental rollout to production **(PREMIUM ALL)**
## Incremental rollout to production
DETAILS:
**Tier:** Premium, Ultimate
**Offering:** SaaS, self-managed
Use an incremental rollout to continuously deploy your application,
starting with only a few pods. You can increase the number of pods
......@@ -313,7 +321,11 @@ With `INCREMENTAL_ROLLOUT_MODE` set to `manual` and with `STAGING_ENABLED`:
![Rollout and staging enabled](img/rollout_staging_enabled.png)
## Timed incremental rollout to production **(PREMIUM ALL)**
## Timed incremental rollout to production
DETAILS:
**Tier:** Premium, Ultimate
**Offering:** SaaS, self-managed
Use a timed incremental rollout to continuously deploy your application, starting with
only a few pods.
......
......@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Use Auto DevOps to deploy to EC2
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216008) in GitLab 13.6.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216008) in GitLab 13.6.
To use [Auto DevOps](../index.md) to deploy to EC2:
......
......@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Use Auto DevOps to deploy to Amazon ECS
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/208132) in GitLab 13.0.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/208132) in GitLab 13.0.
You can choose to target AWS ECS as a deployment platform instead of using Kubernetes.
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Use Auto DevOps to deploy an application to Google Kubernetes Engine **(FREE ALL)**
# Use Auto DevOps to deploy an application to Google Kubernetes Engine
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
In this tutorial, we'll help you to get started with [Auto DevOps](../index.md)
through an example of how to deploy an application to Google Kubernetes Engine (GKE).
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Customize Auto DevOps **(FREE ALL)**
# Customize Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
You can customize components of Auto DevOps to fit your needs. For example, you can:
......@@ -45,7 +49,7 @@ You can customize your buildpacks when either:
### Customize buildpacks with Cloud Native Buildpacks
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28165) in GitLab 12.10.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28165) in GitLab 12.10.
Specify either:
......@@ -164,7 +168,7 @@ You can extend and manage your Auto DevOps configuration with GitLab APIs:
## Forward CI/CD variables to the build environment
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/25514) in GitLab 12.3.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/25514) in GitLab 12.3.
To forward CI/CD variables to the build environment, add the names of the variables
you want to forward to the `AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES` CI/CD variable.
......@@ -219,7 +223,7 @@ repository or by specifying a project CI/CD variable:
### Customize Helm chart values
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30628) in GitLab 12.6, `.gitlab/auto-deploy-values.yaml` is used by default for Helm upgrades.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30628) in GitLab 12.6, `.gitlab/auto-deploy-values.yaml` is used by default for Helm upgrades.
To override the default values in the `values.yaml` file in the
[default Helm chart](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/tree/master/assets/auto-deploy-app), either:
......@@ -374,7 +378,7 @@ To use the old PostgreSQL, set the `AUTO_DEVOPS_POSTGRES_CHANNEL` variable to
### Customize values for PostgreSQL Helm Chart
> [Introduced](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/issues/113) in GitLab 13.8 with auto-deploy-image v2.
> - [Introduced](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/issues/113) in GitLab 13.8 with auto-deploy-image v2.
To set custom values, do one of the following:
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Auto DevOps **(FREE ALL)**
# Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38366) in GitLab 11.0.
> - Support for the GitLab agent was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/299350) in GitLab 14.5.
......@@ -115,7 +119,7 @@ To disable it, follow the same process and clear the
#### At the group level
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/52447) in GitLab 11.10.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/52447) in GitLab 11.10.
When you enable Auto DevOps at the group level, the subgroups and
projects in that group inherit the configuration. You can save time by
......@@ -148,7 +152,11 @@ Auto DevOps pipeline for any project that belongs to that group:
1. Select **Build > Pipelines**.
1. To trigger the Auto DevOps pipeline, select **Run pipeline**.
#### At the instance level **(FREE SELF)**
#### At the instance level
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
To enable Auto DevOps by default for all projects, you can enable it at the instance level.
You can still disable Auto DevOps for each group and project
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Multiple Kubernetes clusters for Auto DevOps **(FREE ALL)**
# Multiple Kubernetes clusters for Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
When using Auto DevOps, you can deploy different environments to different Kubernetes clusters.
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Prepare Auto DevOps for deployment **(FREE ALL)**
# Prepare Auto DevOps for deployment
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
If you enable Auto DevOps without setting the base domain and deployment
strategy, GitLab can't deploy your application directly. Therefore, we
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Requirements for Auto DevOps **(FREE ALL)**
# Requirements for Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
Before enabling [Auto DevOps](index.md), we recommend you to prepare it for
deployment. If you don't, you can use it to build and test your apps, and
......@@ -27,7 +31,7 @@ To prepare the deployment:
## Auto DevOps deployment strategy
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38542) in GitLab 11.0.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38542) in GitLab 11.0.
When using Auto DevOps to deploy your applications, choose the
[continuous deployment strategy](../../ci/index.md)
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Stages of Auto DevOps **(FREE ALL)**
# Stages of Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
The following sections describe the stages of [Auto DevOps](index.md).
Read them carefully to understand how each one works.
......@@ -188,7 +192,7 @@ might want to use a [custom buildpack](customize.md#custom-buildpacks).
## Auto Code Quality
> [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212499) from GitLab Starter to GitLab Free in 13.2.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212499) from GitLab Starter to GitLab Free in 13.2.
Auto Code Quality uses the
[Code Quality image](https://gitlab.com/gitlab-org/ci-cd/codequality) to run
......@@ -227,7 +231,11 @@ warnings on [Ultimate](https://about.gitlab.com/pricing/) licenses.
For more information, see [Secret Detection](../../user/application_security/secret_detection/index.md).
## Auto Dependency Scanning **(ULTIMATE ALL)**
## Auto Dependency Scanning
DETAILS:
**Tier:** Ultimate
**Offering:** SaaS, self-managed
Dependency Scanning runs analysis on the project's dependencies and checks for potential security issues.
The Auto Dependency Scanning stage is skipped on licenses other than
......@@ -289,7 +297,11 @@ deploys with Auto DevOps can undo your changes. Also, if you change something
and want to undo it by deploying again, Helm may not detect that anything changed
in the first place, and thus not realize that it needs to re-apply the old configuration.
## Auto DAST **(ULTIMATE ALL)**
## Auto DAST
DETAILS:
**Tier:** Ultimate
**Offering:** SaaS, self-managed
Dynamic Application Security Testing (DAST) uses the popular open source tool
[OWASP ZAProxy](https://github.com/zaproxy/zaproxy) to analyze the current code
......@@ -330,9 +342,13 @@ You can disable DAST:
- Only on feature branches by setting `REVIEW_DISABLED` variable to
`"true"`. This also disables the Review App.
## Auto Browser Performance Testing **(PREMIUM ALL)**
## Auto Browser Performance Testing
> Introduced in GitLab 10.4.
DETAILS:
**Tier:** Premium, Ultimate
**Offering:** SaaS, self-managed
> - Introduced in GitLab 10.4.
Auto [Browser Performance Testing](../../ci/testing/browser_performance_testing.md)
measures the browser performance of a web page with the
......@@ -351,9 +367,13 @@ file named `.gitlab-urls.txt` in the root directory, one file per line. For exam
Any browser performance differences between the source and target branches are also
[shown in the merge request widget](../../ci/testing/browser_performance_testing.md).
## Auto Load Performance Testing **(PREMIUM ALL)**
## Auto Load Performance Testing
DETAILS:
**Tier:** Premium, Ultimate
**Offering:** SaaS, self-managed
> Introduced in GitLab 13.2.
> - Introduced in GitLab 13.2.
Auto [Load Performance Testing](../../ci/testing/load_performance_testing.md)
measures the server performance of an application with the
......@@ -370,7 +390,7 @@ Any load performance test result differences between the source and target branc
## Auto Deploy
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216008) in GitLab 13.6, you have the choice to deploy to [Amazon Elastic Compute Cloud (Amazon EC2)](https://aws.amazon.com/ec2/) in addition to a Kubernetes cluster.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216008) in GitLab 13.6, you have the choice to deploy to [Amazon Elastic Compute Cloud (Amazon EC2)](https://aws.amazon.com/ec2/) in addition to a Kubernetes cluster.
Auto Deploy is an optional step for Auto DevOps. If the [requirements](requirements.md) are not met, the job is skipped.
......@@ -413,7 +433,7 @@ to upgrade your environments before upgrading to GitLab 14.0.
### GitLab deploy tokens
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/19507) in GitLab 11.0.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/19507) in GitLab 11.0.
[GitLab Deploy Tokens](../../user/project/deploy_tokens/index.md#gitlab-deploy-token)
are created for internal and private projects when Auto DevOps is enabled, and the
......@@ -472,7 +492,7 @@ deletion).
### Migrations
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/21955) in GitLab 11.4
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/21955) in GitLab 11.4
You can configure database initialization and migrations for PostgreSQL to run
within the application pod by setting the project CI/CD variables `DB_INITIALIZE` and
......@@ -578,7 +598,7 @@ When using Cloud Native Buildpacks, instead of `/bin/herokuish procfile exec`, u
## Auto Code Intelligence
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216438) in GitLab 13.5.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216438) in GitLab 13.5.
[GitLab code intelligence](../../user/project/code_intelligence.md) adds
code navigation features common to interactive development environments (IDE),
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Troubleshooting Auto DevOps **(FREE ALL)**
# Troubleshooting Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
The information in this documentation page describes common errors when using
Auto DevOps, and any available workarounds.
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Upgrading deployments for newer Auto Deploy dependencies **(FREE ALL)**
# Upgrading deployments for newer Auto Deploy dependencies
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
[Auto Deploy](stages.md#auto-deploy) is a feature that deploys your application to a Kubernetes cluster.
It consists of several dependencies:
......@@ -77,7 +81,7 @@ Kubernetes cluster, follow your cloud provider's instructions. Here's
#### Helm v3
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/228609) in GitLab 13.4.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/228609) in GitLab 13.4.
The `auto-deploy-image` uses the Helm binary to manipulate the releases.
Previously, `auto-deploy-image` used Helm v2, which used Tiller in a cluster.
......@@ -125,7 +129,7 @@ with the [v1 auto-deploy-image](#use-a-specific-version-of-auto-deploy-dependenc
#### Traffic routing change for canary deployments and incremental rollouts
> [Introduced](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/merge_requests/109) in GitLab 13.4.
> - [Introduced](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/merge_requests/109) in GitLab 13.4.
Auto Deploy supports advanced deployment strategies such as [canary deployments](cicd_variables.md#deploy-policy-for-canary-environments)
and [incremental rollouts](../../ci/environments/incremental_rollouts.md).
......
......@@ -4,7 +4,11 @@ group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Upgrading PostgreSQL for Auto DevOps **(FREE ALL)**
# Upgrading PostgreSQL for Auto DevOps
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
When `POSTGRES_ENABLED` is `true`, Auto DevOps provides an
[in-cluster PostgreSQL database](customize.md#postgresql-database-support) for your application.
......
......@@ -5,7 +5,11 @@ description: Runners, jobs, pipelines, variables.
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Use CI/CD to build your application **(FREE ALL)**
# Use CI/CD to build your application
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** SaaS, self-managed
Use CI/CD to generate your application.
......
......@@ -4,7 +4,7 @@ group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Cherry-pick a Git commit **(FREE ALL)**
# Cherry-pick a Git commit
In Git, you can *cherry-pick* a commit (a set of changes) from an existing branch,
and apply those changes to another branch. Cherry-picks can help you:
......
......@@ -5,7 +5,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated
description: "Introduction to Git rebase and force push, methods to resolve merge conflicts through the command line."
---
# Git rebase and force push **(FREE ALL)**
# Git rebase and force push
In Git, a rebase updates your branch with the contents of another branch.
A rebase confirms that changes in your branch don't conflict with
......
......@@ -4,7 +4,7 @@ group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Installing Git **(FREE ALL)**
# Installing Git
To begin contributing to GitLab projects, you must download and install the Git client on your computer.
......
......@@ -5,7 +5,7 @@ description: Common commands and workflows.
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
---
# Learn Git **(FREE ALL)**
# Learn Git
Git is a [free and open source](https://git-scm.com/about/free-and-open-source)
distributed version control system. It handles projects of all sizes quickly and
......
......@@ -4,7 +4,7 @@ group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
---
# Git Large File Storage (LFS) **(FREE ALL)**
# Git Large File Storage (LFS)
Managing large files such as audio, video and graphics files has always been one
of the shortcomings of Git. The general recommendation is to not have Git repositories
......@@ -18,7 +18,11 @@ In the repository view, files tracked by Git LFS display an **LFS** badge next t
![Git LFS tracking status](img/lfs_badge_v16_0.png)
## Configure your GitLab server for Git LFS **(FREE SELF)**
## Configure your GitLab server for Git LFS
DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
To install Git LFS on your self-managed GitLab server, see
[GitLab Git Large File Storage (LFS) Administration](../../../administration/lfs/index.md).
......
......@@ -4,7 +4,7 @@ group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Undo options in Git **(FREE ALL)**
# Undo options in Git
Git provides options for undoing changes. The method for undoing a change depends on whether the change is unstaged, staged, committed, or pushed.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment