mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-27 05:28:22 +00:00
Fix tables of contents, headers and formatting
This commit is contained in:
@@ -34,25 +34,12 @@ Rancher's pipeline provides a simple CI/CD experience, but it does not offer the
|
||||
|
||||
:::
|
||||
|
||||
This section covers the following topics:
|
||||
|
||||
- [Concepts](#concepts)
|
||||
- [How Pipelines Work](#how-pipelines-work)
|
||||
[Roles-based Access Control for Pipelines](#role-based-access-control-for-pipelines)
|
||||
- [Setting up Pipelines](#setting-up-pipelines)
|
||||
- [Configure version control providers](#1-configure-version-control-providers)
|
||||
- [Configure repositories](#2-configure-repositories)
|
||||
- [Configure the pipeline](#3-configure-the-pipeline)
|
||||
- [Pipeline Configuration Reference](#pipeline-configuration-reference)
|
||||
- [Running your Pipelines](#running-your-pipelines)
|
||||
- [Triggering a Pipeline](#triggering-a-pipeline)
|
||||
- [Modifying the Event Triggers for the Repository](#modifying-the-event-triggers-for-the-repository)
|
||||
|
||||
# Concepts
|
||||
## Concepts
|
||||
|
||||
For an explanation of concepts and terminology used in this section, refer to [this page.](../reference-guides/pipelines/concepts.md)
|
||||
|
||||
# How Pipelines Work
|
||||
## How Pipelines Work
|
||||
|
||||
After enabling the ability to use pipelines in a project, you can configure multiple pipelines in each project. Each pipeline is unique and can be configured independently.
|
||||
|
||||
@@ -86,7 +73,7 @@ When you configure a pipeline in one of your projects, a namespace specifically
|
||||
|
||||
:::
|
||||
|
||||
# Role-based Access Control for Pipelines
|
||||
## Role-based Access Control for Pipelines
|
||||
|
||||
If you can access a project, you can enable repositories to start building pipelines.
|
||||
|
||||
@@ -94,7 +81,7 @@ Only [administrators](../how-to-guides/advanced-user-guides/authentication-permi
|
||||
|
||||
Project members can only configure repositories and pipelines.
|
||||
|
||||
# Setting up Pipelines
|
||||
## Setting up Pipelines
|
||||
|
||||
### Prerequisite
|
||||
|
||||
@@ -241,7 +228,7 @@ Now that repositories are added to your project, you can start configuring the p
|
||||
**Results:** Your pipeline is now configured and ready to be run.
|
||||
|
||||
|
||||
# Pipeline Configuration Reference
|
||||
## Pipeline Configuration Reference
|
||||
|
||||
Refer to [this page](../reference-guides/pipelines/pipeline-configuration.md) for details on how to configure a pipeline to:
|
||||
|
||||
@@ -260,7 +247,7 @@ The configuration reference also covers how to configure:
|
||||
- Secrets
|
||||
|
||||
|
||||
# Running your Pipelines
|
||||
## Running your Pipelines
|
||||
|
||||
Run your pipeline for the first time. Find your pipeline and select the vertical **⋮ > Run**.
|
||||
|
||||
@@ -272,7 +259,7 @@ During this initial run, your pipeline is tested, and the following pipeline com
|
||||
|
||||
This process takes several minutes. When it completes, you can view each pipeline component from the project **Workloads** tab.
|
||||
|
||||
# Triggering a Pipeline
|
||||
## Triggering a Pipeline
|
||||
|
||||
When a repository is enabled, a webhook is automatically set in the version control provider. By default, the pipeline is triggered by a **push** event to a repository, but you can modify the event(s) that trigger running the pipeline.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user