2

I have a working Tekton Pipeline that is successfully triggered by a GitHub webhook, but it doesn't work with Gitlab webhook. I can see that the Gitlab webhook is triggered and that it gets to the EventListener container in OpenShift, but the Pipeline itself does not run. So, does it work with Gitlab webhooks? If so, is there something that I need to setup or change so that it actually triggers the pipeline?

Thanks! Cesar

2

1 Answer 1

1

A Tekton Trigger can initiated by any http-request, so if you use a GitHub-webhook, a GitLab webhook or a curl command should not matter.

However, those webhook requests provide data in a slightly different json-format, so to pass parameters to the Pipeline, you need to properly configure the TriggerBinding matching the request that you receive. You probably need a different TriggerBinding for GitLab than for GitHub.

but the Pipeline itself does not run

it is hard to answer this part without more information. Any error message?

Sign up to request clarification or add additional context in comments.

2 Comments

Thank you Jonas! I don't see errors in any of the containers logs (tekton-triggers-webhook, tekton-triggers-controller, tekton-pipelines-controller, tekton-pipelines-webhook). Is there somewhere else that I should look for?
Yeah, you should have a look into the EventListener pod's logs. Grab the name via kubectl get pods (it's derived from the contents of your EventListener's metadata: name: field prefixed by el-). Assuming this gives a el-gitlab-listener-db6bb5858-dc8ks 1/1 Running 0 17m, then you can grab the logs via k logs po el-gitlab-listener-db6bb5858-dc8ks.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.