-
Notifications
You must be signed in to change notification settings - Fork 420
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
EventListener Unsupported Protocol Scheme Error #1772
Comments
Did you choose non Json Webhook? |
No..it's JSON
|
I tried recreating this using the following example: https://github.com/tektoncd/triggers/tree/main/examples/v1beta1/github-add-changed-files-push-cel Above error isn't happening. I configured the above example with a repo. |
Can you please provide some more concrete example where we can recreate this? |
I’ve set it up on OpenShift, and here is the configuration I used for the triggers.
when i'm removing the inteceptor, its working fine
|
@savitaashture Can you look into this? |
Hi @sidharthsudheer20 i tried your example and i don't see any such errors Interceptor pod log:
EL pod log
|
@savitaashture Can you provide me the core interceptor configuration ? |
I just had the same error on a fresh cluster, with a "known good" configuration. For debugging, I messed around in the Trigger yaml, added/removed sections, disabled "enabled: true" and enabled it again, and it magically worked after that.
Tekton deployed using ArgoCD. Random guess: maybe there is some timing issue that causes addChangedFiles to break when not all of Tekton is running yet? |
EventListener Unsupported Protocol Scheme Error
Expected Behavior
The Tekton EventListener should correctly process incoming GitHub webhook events without errors, properly identifying and handling the protocol.
Actual Behavior
The Tekton EventListener fails to process GitHub webhook events and logs the error:
Steps to Reproduce the Issue
Additional Information
Kubernetes Version:
Tekton Pipeline Version:
EventListener Configuration:
Logs:
The text was updated successfully, but these errors were encountered: