-
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
"From" does not work #755
Comments
@vdemeester |
@vincent-pli Seems like a document issue. AFAIK, we need to provide resource filed which will be the resource name from the previous task, so your changed input resources for the second task looks fine to me. Can you please point me where the yaml's are. More @vdemeester can give us info about this. Thanks |
Thanks @piyush-garg , I just follow document about |
Ok, Thanks @vincent-pli will fix that. For your reference, here is an example with the details I provided https://github.com/tektoncd/pipeline/blob/master/docs/tutorial.md#pipeline @vdemeester Any thoughts. |
Yaml provided as a sample have missing property and are confusing the users Fix them to avoid confusions and also used the consistent naming Fixes tektoncd#755
Yaml provided as a sample have missing property and are confusing the users Fix them to avoid confusions and also used the consistent naming Fixes #755
Replace busybox image url
Expected Behavior
This my pipeline:
I guess it's right, just follow the guide, I expect the task will run as build-model-image -> train
Actual Behavior
I get error:
pipelineTask tried to use input resource not present in declared resources
Additional Info
I try to figure out what happened, then find the code in pkg/reconciler/v1alpha1/pipelinerun/resources/pipelinerunresolution.go
I don't know, the logic is not right, then I try to add additional code(the comment ones) and I get a memory error in
pkg/reconciler/v1alpha1/pipelinerun/resources/pipelinerunresolution.ValidateFrom
at the end, I pass the issue by add additional item in inputs section of the second task:
from:
to:
So is this issue just a document error?
The text was updated successfully, but these errors were encountered: