You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixestektoncd#6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.
This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks.
This commit also refactors the common code to a PipelineTask SetDefaults function.
/kind bug
[tektoncd#6449]: tektoncd#6449
Fixestektoncd#6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.
This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks.
This commit also refactors the common code to a PipelineTask SetDefaults function.
/kind bug
[tektoncd#6449]: tektoncd#6449
Fixes#6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.
This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks.
This commit also refactors the common code to a PipelineTask SetDefaults function.
/kind bug
[#6449]: #6449
Expected Behavior
Default Resolver is set for Finally Tasks
Actual Behavior
Default Resolver is not set for Finally Tasks
Additional Info
Was looking into the
SetDefaults
function and realized that support for default Resolver is not implemented for Finally Tasks:pipeline/pkg/apis/pipeline/v1/pipeline_defaults.go
Lines 34 to 65 in 9ff4f88
Related PR: #6317
cc @QuanZhang-William
The text was updated successfully, but these errors were encountered: