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

PipelineRuns should show parameters and results #1570

Open
bitsofinfo opened this issue Jun 25, 2020 · 10 comments
Open

PipelineRuns should show parameters and results #1570

bitsofinfo opened this issue Jun 25, 2020 · 10 comments
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@bitsofinfo
Copy link

bitsofinfo commented Jun 25, 2020 •
edited by AlanGreene
Loading

Using latest version: PipelineRuns, when I click on a PipelineRun, i see its taskruns + their params and results.... but I don't see the params or results for the PipelineRun itself.
@bitsofinfo bitsofinfo added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 25, 2020
@AlanGreene
Copy link
Member

Thanks for raising this request. It's something we're planning to do as part of a larger set of changes to the PipelineRun / TaskRun pages including #487, #762, better integration of Triggers, etc.

Some of this work is already in progress. I'll update the issue with designs etc. as soon as they're ready.

@tekton-robot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

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

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 15, 2020
@AlanGreene
Copy link
Member

/remove-lifecycle rotten
/reopen

@tekton-robot tekton-robot reopened this Aug 15, 2020
@tekton-robot
Copy link
Contributor

@AlanGreene: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 15, 2020
@tekton-robot
Copy link
Contributor

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 Jan 11, 2021
@AlanGreene
Copy link
Member

This is still something we want to do, freezing so it doesn't get auto-closed.

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 12, 2021
@AlanGreene AlanGreene mentioned this issue Mar 3, 2021
Closed
@AlanGreene AlanGreene changed the title PipelineRuns should show parameters PipelineRuns should show parameters and results Mar 10, 2021
@AlanGreene
Copy link
Member

AlanGreene commented Mar 10, 2021 •
edited
Loading

Updated title + description to also cover PipelineRun results as requested in #1943 (comment) and by a number of users on Slack.

Once #762 is done we should be able to easily tackle this one.

@AlanGreene AlanGreene mentioned this issue Feb 10, 2022
Open
16 tasks
@AlanGreene
Copy link
Member

/area roadmap

@tekton-robot tekton-robot added the area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) label Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Tekton Community Roadmap
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bitsofinfo @AlanGreene @steveodonovan @tekton-robot