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

Update Matrix Documentation for Results #7012

Merged
merged 1 commit into from
Aug 7, 2023
Merged

Update Matrix Documentation for Results #7012

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 3 additions & 4 deletions docs/matrix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -358,11 +358,10 @@ tasks:
value: $(tasks.task-2.results.duh.key) # string replacement from object result
```

### Results from fanned out PipelineTasks
### Results from fanned out Matrixed PipelineTasks

Consuming `Results` from fanned out `PipelineTasks` will not be in the supported in the initial iteration
of `Matrix`. Supporting consuming `Results` from fanned out `PipelineTasks` will be revisited after array
and object `Results` are supported.
Emitting `Results` from fanned out `PipelineTasks` is not currently supported.
We plan to support emitting `Results` from fanned out `PipelineTasks` in the near future.


## Retries
Expand Down
2 changes: 0 additions & 2 deletions docs/pipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -921,8 +921,6 @@ Array and Object result is a beta feature and can be enabled by setting `enable-

**Note:** Whole Array and Object `Results` (using star notation) cannot be referred in `script`.

**Note:** `Matrix` does not support `object` and `array` results.

When one `Task` receives the `Results` of another, there is a dependency created between those
two `Tasks`. In order for the receiving `Task` to get data from another `Task's` `Result`,
the `Task` producing the `Result` must run first. Tekton enforces this `Task` ordering
Expand Down
Loading