-
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
Tekton incorrectly maps pipeline parameters and task outputs with the same name #5988
Comments
hi @typeness ,i think your pipelinerun yml that provided should add
after modified, the pipelinerun yml should be like this:
after executed, will get the result: If you move the task print-msg-2 before print-msg, will get the result: |
Hello @chengjoey, thanks for your comment. As I understand you provided a workaround but still consider this a valid issue. The pipeline used to work in Tekton 0.36 |
In Tekton 0.36, if you set |
Thanks @chengjoey for quick turn around. Is it at all possible to backport this fix to 0.41.x? |
Yes, the cherry-pick has been opened on #6032 |
Expected Behavior
The pipeline run should correctly map pipeline parameters and task outputs with the same name.
Regression: This scenario works correctly on v0.36.
Actual Behavior
The
print-msg-2
task has thestart, step, end
parameters which are pipeline parameters with the same name.The
print-msg
task has thestart, step, end
parameters which are outputs from other tasks with the same nameIn runtime both
print-msg
andprint-msg-2
tasks parameters are incorrectly mapped to task outputsSteps to Reproduce the Problem
Additional Info
Client Version: v1.26.0
0.41
The text was updated successfully, but these errors were encountered: