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

Epic: User-facing Error Handling Improvement 🧹 #7276

Closed
JeromeJu opened this issue Oct 25, 2023 · 1 comment
Closed

Epic: User-facing Error Handling Improvement 🧹 #7276

JeromeJu opened this issue Oct 25, 2023 · 1 comment
Assignees
Labels
Epic Issues that should be considered as Epics (aka multiple sub-tasks, …) kind/feature Categorizes issue or PR as related to a new feature.

Comments

@JeromeJu
Copy link
Member

JeromeJu commented Oct 25, 2023

Context

This issue tracks the improvement of error handling for pipeline as an epic. This includes improving the user-facing error messages, differentiating expected/ runtime errors and cleanups. It aims to improve the debug experience involving cluster operators, service providers and end users building on Tekton.

Note that the users include service provider and cluster operator.

Reference of errors for stakeholders:

  • Logging error reference for cluster operators and service providers.
  • User-facing error cleanup (to examine whether the existing messages are sufficient).

Work plan:

Differentiating user versus system errors:

Better User-facing Error Reference and Messages:

Validation

Fix edge cases:

Future work identified

Nice-to-have

Go style cleanups:

@JeromeJu JeromeJu added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 25, 2023
@tekton-robot
Copy link
Collaborator

@JeromeJu: The label(s) kind/area/epic cannot be applied, because the repository doesn't have them.

In response to this:

/kind area/epic

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.

@JeromeJu JeromeJu changed the title Error Handling Improvement 🧹 Epic: Error Handling Improvement 🧹 Oct 25, 2023
@JeromeJu JeromeJu changed the title Epic: Error Handling Improvement 🧹 Epic: User-facing Error Handling Improvement 🧹 Oct 25, 2023
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Nov 13, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed due to a
user error or not.

This is a step 1 for tektoncd#6859

part of  tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Nov 13, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed due to a
user error or not.

This is a step 1 for tektoncd#6859

part of  tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 8, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 8, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 10, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 11, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 14, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 19, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Dec 21, 2023
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 3, 2024
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 3, 2024
This commit follows up tektoncd#7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 4, 2024
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of tektoncd#7276
tekton-robot pushed a commit that referenced this issue Jan 16, 2024
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.

/kind misc
part of #7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 17, 2024
This commit follows up tektoncd#7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 17, 2024
This commit follows up tektoncd#7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 24, 2024
This commit follows up tektoncd#7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of tektoncd#7276
JeromeJu added a commit to JeromeJu/pipeline that referenced this issue Jan 24, 2024
This commit follows up tektoncd#7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of tektoncd#7276
tekton-robot pushed a commit that referenced this issue Jan 30, 2024
This commit follows up #7475 and labels user error for failed TaskRun
status messages. It marks off user errors in the taskrun reconciler and
communicate to users via TaskRunStatus condition messages.

/kind misc
part of #7276
@JeromeJu JeromeJu added the Epic Issues that should be considered as Epics (aka multiple sub-tasks, …) label Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Issues that should be considered as Epics (aka multiple sub-tasks, …) kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants