-
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
Conversion error for parameters when pipelineref.bundle is used #5500
Comments
/assign |
@lbernick what version does it affect ? |
Looks like it's the stored version as of v1beta1 according to #5506 (comment). |
I think @vdemeester might be asking about the software version not the api version (to know if we need to backport)-- is that right? I think this change was introduced in 0.39.0 so at least we only have to do one backport 😬 |
@lbernick ah yeah I should have been more clear. And yes, which release, to know if I need to make the PR fixing this in 0.40.0 milestone or not 👼🏼 |
Yes let's include it in the 0.40.0 milestone and backport to 0.39.0 |
Well, 0.40.1.. 😅 for some reason I thought it was merged when I chose the commit to be released on.. 🤦🏼 |
@vdemeester
Installed
|
hum 🤔 #5506 defenitely got in 0.40.1 though. |
@vdemeester Please let me know how if I can help to debug it
PR
|
pipeline
|
Ah ok, it's using the |
@mike-serchenia but indeed, your bug is still there, I'll re-open and update the title. |
(We also need to validate if this is also happening for spec coming out of resolvers) |
i was checking requirements to use resolvers A cluster with the alpha feature gate enabled could be an issue since GKE Alpha has the following limitations to be more specific:
|
Hey @mike-serchenia, just two quick notes--
hope this is helpful! |
the same problem still exists in v.0.50.2; Tekton can not be used because of this problem. |
Hi @tirelibirefe , thanks for your report! Would you mind provide more details on the Pipeline/Task that you are running that we might be able take a look into it? |
Hello @JeromeJu |
Webhook error messages show:
I believe the issue is that param value conversion doesn't handle param type "" (i.e. param type not set-- corresponds to string type)
The text was updated successfully, but these errors were encountered: