Fix Pipeline error with ClusterTasks #1003
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
It is possible to use
ClusterTask
in a Pipeline, for that youspecify that the
Task
you want to use is of typeClusterTask
(default beingTask
). But, before this change, thePipelineRun
using thisPipeline
would fail as theKind
information is not passed from the
PipelineTask.TaskRef
to theactual
TaskRun
.This fixes that by passing the
Kind
of aTaskRef
when resolvingthe
Task
/TaskRun
in thePipelineRun
reconcilier.A yaml test is added as a regression test.
Fixes #1001 — thanks for the report @steveodonovan
/cc @bobcatfish
Signed-off-by: Vincent Demeester [email protected]
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.
Release Notes