-
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
Cannot assign params with task results to other task value #2387
Comments
/kind bug |
I think the problem is here: https://github.com/tektoncd/pipeline/blob/master/pkg/apis/pipeline/v1alpha1/pipeline_validation.go#L143-L150 In this block we extract all variable substitutions: |
will take a look at this. |
/close |
@vdemeester: Closing this issue. 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. |
This was partially addressed in tektoncd#2387 however the example from the bug (tektoncd#2387) was using runAfter, and it should be possible to determine the correct graph without runAfter. The logic that was determining the graph was returning an error if any of the substitutions present in a string along with a result were not results. Now we will instead ignore these substitutions. We might want to revisit the validation to make sure that invalid results substitutions are still caught. Also updated some tests so that they will actually compare want against desired; previously if expression parsing failed this part would be skipped and no error would be raised.
This was partially addressed in tektoncd#2387 however the example from the bug (tektoncd#2387) was using runAfter, and it should be possible to determine the correct graph without runAfter. The logic that was determining the graph was returning an error if any of the substitutions present in a string along with a result were not results. Now we will instead ignore these substitutions. We might want to revisit the validation to make sure that invalid results substitutions are still caught.
This was partially addressed in #2387 however the example from the bug (#2387) was using runAfter, and it should be possible to determine the correct graph without runAfter. The logic that was determining the graph was returning an error if any of the substitutions present in a string along with a result were not results. Now we will instead ignore these substitutions. We might want to revisit the validation to make sure that invalid results substitutions are still caught.
(cherry picked from commit b817a12) Removed changes from the cherry picked commit that used PipelineResults
This was partially addressed in tektoncd#2387 however the example from the bug (tektoncd#2387) was using runAfter, and it should be possible to determine the correct graph without runAfter. The logic that was determining the graph was returning an error if any of the substitutions present in a string along with a result were not results. Now we will instead ignore these substitutions. We might want to revisit the validation to make sure that invalid results substitutions are still caught. (cherry picked from commit 4b1b761) Updated test logic that used builder which were added / changed in other commits on master.
(cherry picked from commit b817a12) Removed changes from the cherry picked commit that used PipelineResults
This was partially addressed in #2387 however the example from the bug (#2387) was using runAfter, and it should be possible to determine the correct graph without runAfter. The logic that was determining the graph was returning an error if any of the substitutions present in a string along with a result were not results. Now we will instead ignore these substitutions. We might want to revisit the validation to make sure that invalid results substitutions are still caught. (cherry picked from commit 4b1b761) Updated test logic that used builder which were added / changed in other commits on master.
Expected Behavior
I can assign params with task results to other task value:
Actual Behavior
Cannot assign params with task results to other task value. Error message is generated:
Steps to Reproduce the Problem
pipeline.yaml:
Executing this pipelinerun generates error message:
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
The text was updated successfully, but these errors were encountered: