From 8a32ec4ccaf0a2b119f55604bd72d946590bf73c Mon Sep 17 00:00:00 2001 From: Vincent Demeester Date: Wed, 3 Feb 2021 11:23:23 +0100 Subject: [PATCH] Renaming branches: handling pipeline repository Changing links to any reference to tektoncd/pipeline. Signed-off-by: Vincent Demeester --- content/en/docs/Getting Started/_index.md | 4 ++-- content/en/docs/Overview/_index.md | 16 ++++++++-------- sync/config/pipelines.yaml | 4 ++-- tutorials/katacoda/dashboard/step1.md | 2 +- tutorials/katacoda/playground/step1.md | 4 ++-- 5 files changed, 15 insertions(+), 15 deletions(-) diff --git a/content/en/docs/Getting Started/_index.md b/content/en/docs/Getting Started/_index.md index 2e98f4f..eabdd00 100644 --- a/content/en/docs/Getting Started/_index.md +++ b/content/en/docs/Getting Started/_index.md @@ -46,11 +46,11 @@ kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline ``` Replace `YOUR-VERSION` with the release you prefer. [You can find the full list -of official Tekton releases on GitHub](https://github.com/tektoncd/pipeline/releases). +of official Tekton releases on GitHub](https://github.com/tektoncd/pipeline/releases). Additionally, Tekton Pipelines pushes nightly releases every night to `gcr.io/tekton-nightly`. If you are feeling adventurous and would like to -experiment with the most recent, unreleased code, see [Tekton Development Guide](https://github.com/tektoncd/pipeline/blob/master/DEVELOPMENT.md). +experiment with the most recent, unreleased code, see [Tekton Development Guide](https://github.com/tektoncd/pipeline/blob/main/DEVELOPMENT.md). {{% /alert %}} It may take a few moments before the installation completes. You can check diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md index b756927..7257787 100644 --- a/content/en/docs/Overview/_index.md +++ b/content/en/docs/Overview/_index.md @@ -46,9 +46,9 @@ Tekton provides the following benefits to builders and users of CI/CD systems: Tekton consists of the following components: -- **[Tekton Pipelines](https://github.com/tektoncd/pipeline/blob/master/docs/README.md)** is the foundation of Tekton. It +- **[Tekton Pipelines](https://github.com/tektoncd/pipeline/blob/main/docs/README.md)** is the foundation of Tekton. It defines a set of Kubernetes [Custom Resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) - that act as building blocks from which you can assemble CI/CD pipelines. + that act as building blocks from which you can assemble CI/CD pipelines. - **[Tekton Triggers](https://github.com/tektoncd/triggers/blob/main/README.md)** allows you to instantiate pipelines based on events. For example, you can trigger the instantiation and execution of a pipeline every time a PR is merged against a GitHub repository. You @@ -97,17 +97,17 @@ We also recommend having the following items configured on your Kubernetes clust Tekton introduces the concept of `Tasks`, which specify the workloads you want to run: -- [`Task`](https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md) - defines a series of ordered `Steps`, and each `Step` invokes a specific - build tool on a specific set of inputs and produces a specific set of outputs, which can be used as inputs in the next `Step`. +- [`Task`](https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md) - defines a series of ordered `Steps`, and each `Step` invokes a specific + build tool on a specific set of inputs and produces a specific set of outputs, which can be used as inputs in the next `Step`. -- [`Pipeline`](https://github.com/tektoncd/pipeline/blob/master/docs/pipelines.md) - defines a series of ordered `Tasks`, and just like `Steps` in a +- [`Pipeline`](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md) - defines a series of ordered `Tasks`, and just like `Steps` in a `Task`, a `Task` in a `Pipeline` can use the output of a previously executed `Task` as its input. -- [`TaskRun`](https://github.com/tektoncd/pipeline/blob/master/docs/taskruns.md) - instantiates a specific `Task` to execute on a particular set of +- [`TaskRun`](https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md) - instantiates a specific `Task` to execute on a particular set of inputs and produce a particular set of outputs. In other words, the `Task` tells Tekton what to do, and a `TaskRun` tells Tekton what to do it **on**, as well as any additional details on how to exactly do it, such as build flags. -- [`PipelineRun`](https://github.com/tektoncd/pipeline/blob/master/docs/pipelineruns.md) - instantiates a specific `Pipeline` to execute on a particular +- [`PipelineRun`](https://github.com/tektoncd/pipeline/blob/main/docs/pipelineruns.md) - instantiates a specific `Pipeline` to execute on a particular set of inputs and produce a particular set of outputs to particular destinations. Each `Task` executes in its own Kubernetes Pod. Thus, by default, `Tasks` within a `Pipeline` do not share data. To share data among `Tasks`, @@ -122,4 +122,4 @@ you must explicitly configure each `Task` to make its outputs available to the n ### I want to learn more! -To learn more about the Tekton entities described above and start using Tekton, see the [Tekton Pipelines Overview](https://github.com/tektoncd/pipeline/blob/master/docs/README.md). +To learn more about the Tekton entities described above and start using Tekton, see the [Tekton Pipelines Overview](https://github.com/tektoncd/pipeline/blob/main/docs/README.md). diff --git a/sync/config/pipelines.yaml b/sync/config/pipelines.yaml index a8bec2e..a410713 100644 --- a/sync/config/pipelines.yaml +++ b/sync/config/pipelines.yaml @@ -135,10 +135,10 @@ tags: - deprecations.md - install.md - tutorial.md -- name: master +- name: main # The name to display on tekton.dev. # sync.py will use this value in the version switcher and other places. - displayName: master + displayName: main # Dict of folders to sync folders: docs: diff --git a/tutorials/katacoda/dashboard/step1.md b/tutorials/katacoda/dashboard/step1.md index e586aa9..3cb9f58 100644 --- a/tutorials/katacoda/dashboard/step1.md +++ b/tutorials/katacoda/dashboard/step1.md @@ -10,7 +10,7 @@ Now, let's begin! ## Install the Tekton Dashboard Prerequisites -- [Tekton Pipelines](https://github.com/tektoncd/pipeline/blob/master/docs/install.md) +- [Tekton Pipelines](https://github.com/tektoncd/pipeline/blob/main/docs/install.md) `kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.20.0/release.yaml`{{execute}} Verify the pods are running: diff --git a/tutorials/katacoda/playground/step1.md b/tutorials/katacoda/playground/step1.md index ed973b3..44badc6 100644 --- a/tutorials/katacoda/playground/step1.md +++ b/tutorials/katacoda/playground/step1.md @@ -5,10 +5,10 @@ Please wait while your Tekton playground is starting, this may take a few minute Once it is ready you can check the installed versions: `tkn version`{{execute}} -Try out some of the [examples](https://github.com/tektoncd/pipeline/tree/master/examples) from the Tekton Pipeline repo. +Try out some of the [examples](https://github.com/tektoncd/pipeline/tree/main/examples) from the Tekton Pipeline repo. For example: -`kubectl apply -f https://raw.githubusercontent.com/tektoncd/pipeline/master/examples/v1beta1/pipelineruns/output-pipelinerun.yaml`{{execute}} +`kubectl apply -f https://raw.githubusercontent.com/tektoncd/pipeline/main/examples/v1beta1/pipelineruns/output-pipelinerun.yaml`{{execute}} You can track the progress of the `PipelineRuns` using: -- GitLab