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.

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

Add array of all tasks' results as variable #4589

Closed
HildaHay opened this issue Feb 16, 2022 · 4 comments
Closed

Add array of all tasks' results as variable #4589

HildaHay opened this issue Feb 16, 2022 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@HildaHay
Copy link

Feature request

Right now, each task's result is available as an individual variable. I'd like to have another variable that contains all of the tasks' results as an array.

Use case

When my pipeline fails, I'd like to send the programmer a message telling them which task it failed on, to help them figure out what went wrong without having to check the dashboard if it was a simple problem. Right now, it's possible to do this by passing all the individual task result variables to the message task, but combining them into a single array would make this simpler and easier to maintain.

@HildaHay HildaHay added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 16, 2022
@jerop
Copy link
Member

jerop commented Mar 15, 2022

@HildaHay - Thank you for opening this feature request. We already have a proposal to support array Results: TEP-0076: Expanded array support: results and indexing. This feature request is related to #1393 and #3255.

cc @bobcatfish @wlynch

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2022
@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 13, 2022
@lbernick
Copy link
Member

Array results have been released! They are available starting in v0.38.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants