Update Verify-related docs with tier badges

Add tier badging to Pipeline Execution product docs

Update Verify-related docs with tier badges
Add tier badging to Pipeline Execution product docs
68466165 · Craig Norris · bf08452c · 68466165 · 68466165 · 68466165
Commit 68466165 authored Jun 21, 2021 by Craig Norris
21 changed files
--- a/doc/administration/external_pipeline_validation.md
+++ b/doc/administration/external_pipeline_validation.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference, howto
 ---

-# External pipeline validation
+# External pipeline validation **(FREE SELF)**

 You can use an external service to validate a pipeline before it's created.


--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: index, concepts, howto
 ---

-# Caching in GitLab CI/CD
+# Caching in GitLab CI/CD **(FREE)**

 A cache is one or more files that a job downloads and saves. Subsequent jobs that use
 the same cache don't have to download the files again, so they execute more quickly.

--- a/doc/ci/docker/index.md
+++ b/doc/ci/docker/index.md
@@ -6,9 +6,9 @@ comments: false
 type: index
 ---

-# Docker integration
+# Docker integration **(FREE)**

-There are two primary ways to incorporate [Docker](https://www.docker.com) in your CI/CD workflow.
+There are two primary ways to incorporate [Docker](https://www.docker.com) into your CI/CD workflow:

 - **[Run your CI/CD jobs](using_docker_images.md) in Docker containers.**


--- a/doc/ci/docker/using_docker_build.md
+++ b/doc/ci/docker/using_docker_build.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: concepts, howto
 ---

-# Use Docker to build Docker images
+# Use Docker to build Docker images **(FREE)**

 You can use GitLab CI/CD with Docker to create Docker images.
 For example, you can create a Docker image of your application,

--- a/doc/ci/docker/using_docker_images.md
+++ b/doc/ci/docker/using_docker_images.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: concepts, howto
 ---

-# Run your CI/CD jobs in Docker containers
+# Run your CI/CD jobs in Docker containers **(FREE)**

 You can run your CI/CD jobs in separate, isolated Docker containers.


--- a/doc/ci/docker/using_kaniko.md
+++ b/doc/ci/docker/using_kaniko.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: howto
 ---

-# Use kaniko to build Docker images
+# Use kaniko to build Docker images **(FREE)**

 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45512) in GitLab 11.2. Requires GitLab Runner 11.2 and above.


--- a/doc/ci/enable_or_disable_ci.md
+++ b/doc/ci/enable_or_disable_ci.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: howto
 ---

-# How to enable or disable GitLab CI/CD
+# How to enable or disable GitLab CI/CD **(FREE)**

 To effectively use GitLab CI/CD, you need:


--- a/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
+++ b/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
@@ -11,7 +11,7 @@ date: 2017-08-31

 <!-- vale off -->

-# Test and deploy Laravel applications with GitLab CI/CD and Envoy
+# Test and deploy Laravel applications with GitLab CI/CD and Envoy **(FREE)**

 ## Introduction


--- a/doc/ci/examples/php.md
+++ b/doc/ci/examples/php.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: tutorial
 ---

-# Testing PHP projects
+# Testing PHP projects **(FREE)**

 This guide covers basic building instructions for PHP projects.


--- a/doc/ci/examples/semantic-release.md
+++ b/doc/ci/examples/semantic-release.md
@@ -4,7 +4,7 @@ group: Package
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---

-# Publish npm packages to the GitLab Package Registry using semantic-release
+# Publish npm packages to the GitLab Package Registry using semantic-release **(FREE)**

 This guide demonstrates how to automatically publish npm packages to the [GitLab Package Registry](../../user/packages/npm_registry/index.md) by using [semantic-release](https://github.com/semantic-release/semantic-release).


--- a/doc/ci/git_submodules.md
+++ b/doc/ci/git_submodules.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---

-# Using Git submodules with GitLab CI/CD
+# Using Git submodules with GitLab CI/CD **(FREE)**

 Use [Git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules) to keep
 a Git repository as a subdirectory of another Git repository. You can clone another

--- a/doc/ci/jobs/index.md
+++ b/doc/ci/jobs/index.md
@@ -4,7 +4,7 @@ group: Pipeline Execution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---

-# Jobs
+# Jobs **(FREE)**

 Pipeline configuration begins with jobs. Jobs are the most fundamental element of a `.gitlab-ci.yml` file.


--- a/doc/ci/merge_request_pipelines/index.md
+++ b/doc/ci/merge_request_pipelines/index.md
@@ -6,7 +6,7 @@ type: reference, index
 last_update: 2019-07-03
 ---

-# Pipelines for merge requests
+# Pipelines for merge requests **(FREE)**

 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/15310) in GitLab 11.6.


--- a/doc/ci/parent_child_pipelines.md
+++ b/doc/ci/parent_child_pipelines.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---

-# Parent-child pipelines
+# Parent-child pipelines **(FREE)**

 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/16094) in GitLab 12.7.


--- a/doc/ci/ssh_keys/index.md
+++ b/doc/ci/ssh_keys/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: tutorial
 ---

-# Using SSH keys with GitLab CI/CD
+# Using SSH keys with GitLab CI/CD **(FREE)**

 GitLab currently doesn't have built-in support for managing SSH keys in a build
 environment (where the GitLab Runner runs).

--- a/doc/ci/troubleshooting.md
+++ b/doc/ci/troubleshooting.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---

-# Troubleshooting CI/CD
+# Troubleshooting CI/CD **(FREE)**

 GitLab provides several tools to help make troubleshooting your pipelines easier.


--- a/doc/ci/yaml/gitlab_ci_yaml.md
+++ b/doc/ci/yaml/gitlab_ci_yaml.md
@@ -6,7 +6,7 @@ type: reference
 ---
 <!-- markdownlint-disable MD044 -->
 <!-- vale gitlab.Spelling = NO -->
-# The .gitlab-ci.yml file
+# The .gitlab-ci.yml file **(FREE)**
 <!-- vale gitlab.Spelling = YES -->
 <!-- markdownlint-enable MD044 -->


--- a/doc/ci/yaml/includes.md
+++ b/doc/ci/yaml/includes.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---

-# GitLab CI/CD include examples
+# GitLab CI/CD include examples **(FREE)**

 In addition to the [`includes` examples](README.md#include) listed in the
 [GitLab CI YAML reference](README.md), this page lists more variations of `include`

--- a/doc/ci/yaml/script.md
+++ b/doc/ci/yaml/script.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---

-# GitLab CI/CD script syntax
+# GitLab CI/CD script syntax **(FREE)**

 You can use special syntax in [`script`](README.md#script) sections to:


--- a/doc/development/cicd/cicd_reference_documentation_guide.md
+++ b/doc/development/cicd/cicd_reference_documentation_guide.md
@@ -4,7 +4,7 @@ group: Pipeline Execution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---

-# CI/CD YAML reference style guide
+# CI/CD YAML reference style guide **(FREE)**

 The CI/CD YAML reference uses a standard style to make it easier to use and update.


--- a/doc/development/cicd/index.md
+++ b/doc/development/cicd/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: index, concepts, howto
 ---

-# CI/CD development documentation
+# CI/CD development documentation **(FREE)**

 Development guides that are specific to CI/CD are listed here.