Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix workspace grammatical error #68

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Fix workspace grammatical error #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
295cf84
Fix workspace grammatical error
biya-bi Jun 21, 2024
30cf751
Fix namespace preparation grammatical error
biya-bi Jun 21, 2024
bb107b9
Fix workspace typo in points to ponder
biya-bi Jun 22, 2024
f534e92
Fix typos in pipeline deploy section
biya-bi Jun 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions documentation/modules/ROOT/pages/_partials/_workspaces.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ include::partial$tekton-nav-to-folder.adoc[tags="folder-all,workspaces"]

In many partical usecases of Pipelines it becomes crucial for you to share the filesystem between Tasks and between Steps. The filesystem could typically hold a clone github repostiory, a ConfigMap or a secret.

A Task step and Pipeline task can share a common filesystem via a Tekton `workspace`. This helps Pipelines to pick up changes form one task to another task in the Pipeline workflow.
A Task step and Pipeline task can share a common filesystem via a Tekton `workspace`. This helps Pipelines to pick up changes from one task to another task in the Pipeline workflow.

[#ws-overview]
== Overview
Expand Down Expand Up @@ -288,7 +288,7 @@ If all went well the list directory should show the directory listing of {tutori

- What is a workspace
- How to bind a workspace to a TaskRun using PVC
- How to share the workaapce across multiple TaskRuns
- How to share the workspace across multiple TaskRuns

[#ws-use-cm]
== Using ConfigMap as Workspace
Expand Down Expand Up @@ -473,8 +473,8 @@ include::ROOT:example$greeter-app-deploy.yaml[]
----

<.> The parameters for the Pipeline
<.> A workpace named `source`, we will map it to the PVC`tekton-tutorial-sources` in PipelineRun in upcoming section
<.> A workapce named `maven-settings`, we will map it to ConfigMap `maven-settings` in the PipelineRun in upcming section
<.> A workspace named `source`, we will map it to the PVC`tekton-tutorial-sources` in PipelineRun in upcoming section
<.> A workspace named `maven-settings`, we will map it to ConfigMap `maven-settings` in the PipelineRun in upcoming section
<.> The `buildah` build image task returns a output. We use the that as part of the `--image` parameter to `kn` Task

[#ws-create-pipeline]
Expand Down
2 changes: 1 addition & 1 deletion documentation/modules/ROOT/pages/_partials/namespace-prep.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ kubectl config set-context --current --namespace {chapter-namespace}
----

ifdef::openshift[]
All exercises of this chapter will be done a namesapace `{chapter-namespace}`, lets create the project if not done earlier and switch to the `{chapter-namespace}` namespace:
All exercises of this chapter will be done in a namespace `{chapter-namespace}`, lets create the project if not done earlier and switch to the `{chapter-namespace}` namespace:
endif::[]

As part of this exercise we will need to install the following external tasks and cluster tasks to be installed in the namespace:
Expand Down