Custom Trigger Information for PipelineRuns

[Fabian-K]

Is your feature request related to a problem?

Since 0.27.0 the PipelineRun list shows trigger information in case the run was created using tekton triggers. This is cool, however not all PipelineRuns are created via triggers. I´m thinking of cron jobs (although there is an example of how to do that via triggers as well) or any other client, maybe even just kubectl create. For those PipelineRuns, the dashboard does not show trigger information.

Describe the solution you'd like

It would be cool to be able to attach trigger information which is then displayed by the dashboard to any PipelineRun. Maybe a certain annotation that - if present - is displayed?

Describe alternatives you've considered

n/a

Additional context

Thanks, Fabian

[AlanGreene]

Thanks for the feature request @Fabian-K. Can you please update the description to use the feature request issue template provided? https://raw.githubusercontent.com/tektoncd/dashboard/main/.github/ISSUE_TEMPLATE/feature-request.md

This helps us to understand the motivation behind a request, the problem it's addressing, alternative that might be considered, etc.

This template should be presented when you create a new issue and choose 'Feature request' from the provided options.

[tekton-robot]

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]

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]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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.