From fae3082cc9f0f739d04987d724b6aeec3dd99fe9 Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Mon, 25 Mar 2019 12:13:58 -0700 Subject: [PATCH] small fix in pipelines --- .../rancher/v2.x/en/project-admin/tools/pipelines/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/project-admin/tools/pipelines/_index.md b/content/rancher/v2.x/en/project-admin/tools/pipelines/_index.md index 722918ea5a3..d869a54b726 100644 --- a/content/rancher/v2.x/en/project-admin/tools/pipelines/_index.md +++ b/content/rancher/v2.x/en/project-admin/tools/pipelines/_index.md @@ -169,9 +169,9 @@ _Available as of v2.2.0_ **Result:** After the version control provider is authenticated, you will be automatically re-directed to start [configuring which repositories]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#configuring-repositories) that you want start using with a pipeline. Once a repository is enabled, you can start to [configure the pipeline]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#pipeline-configuration). -## Managing Pipeline Settings +## Managing Global Pipeline Execution Settings -After configuring a version control provider, there are several options that can be configured for all pipelines. +After configuring a version control provider, there are several options that can be configured globally on how [pipelines]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/pipelines/) are executed in Rancher. 1. From the **Global** view, navigate to the project that you want to configure pipelines.