-
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
Task results do not get passed to conditions #2336
Comments
Ah so we're not applying the variable replacement of results inside of conditions? Whoops! Sounds like an easy fix for whoever is keen to work on this 🙏 |
@othomann could you take a look. |
I will take a look. |
@drewbutlerbb4 how did you get the output for |
I added a test to check that the Params inside the condition are substituted. So this test works now, but I want to make sure the output is good as well. |
To get the names of the pods from your pipelinerun: The output will be mixed in with other details about the pods. Does this answer your question? We'd like to see |
Yes, thanks. This answers my question. I finally got it. Working on it. |
Now I have this:
Preparing a PR for it. |
Created #2354 to take care of this issue. |
@sbwsg @bobcatfish do we target 0.11.x for this fix ? |
We could, it's additive. But this isn't a bug fix (in my view), it's a new feature. We never suggested in any docs that results could be used anywhere other than task params. Especially given conditions staying in v1alpha1 I dont feel that this is an urgent problem that we need to address in a patch release. Results also don't substitute in to PipelineResources, for example, but likewise I wouldn't rush to add them there either. It might even be better if it rests in |
Fixed by the merge of #2354. Scott, you can close it, I believe. |
@sbwsg fair :) |
@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. |
thanks @othomann !!! |
Expected Behavior
Conditions receive Task results as condition parameters.
Actual Behavior
Task results do not get passed properly
Steps to Reproduce the Problem
Can be reproduced from this yaml
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Client version: 0.8.0
Pipeline version: v0.11.0-rc2
The text was updated successfully, but these errors were encountered: