-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 tests for failing remote resolution of Pipelines and Tasks #4886
Add tests for failing remote resolution of Pipelines and Tasks #4886
Conversation
Prompted by discussion on tektoncd#4710, though I should have thought of this earlier! This can't verify that the `ResolutionRequest` is handled correctly by its own reconciler, since that's still in a separate project (for now!), but at least we can be sure that the `PipelineRun` and `TaskRun` reconcilers will respond correctly to a failed `ResolutionRequest`. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
/assign @vdemeester |
@abayer: GitHub didn't allow me to assign the following users: chitrangpatel. Note that only tektoncd members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @abayer!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
Prompted by discussion on #4710, though I should have thought of this earlier!
This can't verify that the
ResolutionRequest
is handled correctly by its own reconciler, sincethat's still in a separate project (for now!), but at least we can be sure that the
PipelineRun
and
TaskRun
reconcilers will respond correctly to a failedResolutionRequest
./kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes