Skip to content

Commit

Permalink
Fix sample yaml
Browse files Browse the repository at this point in the history
Yaml provided as a sample have missing property
and are confusing the users

Fix them to avoid confusions and also used the
consistent naming

Fixes #755
  • Loading branch information
piyush-garg authored and tekton-robot committed Apr 15, 2019
1 parent 2a9c7f8 commit 385a537
Showing 1 changed file with 16 additions and 7 deletions.
23 changes: 16 additions & 7 deletions docs/pipelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,8 @@ For example see this `Pipeline` spec:
name: deploy-kubectl
resources:
inputs:
- name: my-image
- name: image
resource: my-image
from:
- build-app
```
Expand Down Expand Up @@ -236,15 +237,17 @@ For example see this `Pipeline` spec:
name: make-test
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
- name: build-app
taskRef:
name: kaniko-build
runAfter:
- test-app
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
```

In this `Pipeline`, we want to test the code before we build from it, but there
Expand Down Expand Up @@ -274,21 +277,24 @@ For example see this `Pipeline` spec:
name: pylint
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
- name: test-app
taskRef:
name: make-test
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
- name: build-app
taskRef:
name: kaniko-build-app
runAfter:
- test-app
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
outputs:
- name: image
resource: my-app-image
Expand All @@ -299,7 +305,8 @@ For example see this `Pipeline` spec:
- test-app
resources:
inputs:
- name: my-repo
- name: workspace
resource: my-repo
outputs:
- name: image
resource: my-frontend-image
Expand All @@ -309,9 +316,11 @@ For example see this `Pipeline` spec:
resources:
inputs:
- name: my-app-image
resource: my-app-image
from:
- build-app
- name: my-frontend-image
resource: my-frontend-image
from:
- build-frontend
```
Expand Down

0 comments on commit 385a537

Please sign in to comment.