tektoncd / triggers

Event triggering with Tekton!
Apache License 2.0
552 stars 416 forks source link

Tekton Trigger Eventlistener bitbucket #1596

Closed tppalani closed 10 months ago

tppalani commented 1 year ago

Hi All,

I'm doing setup for tekton trigger event based on the bitbucket repository branch update. I have created below objects in k8s cluster

  1. EventListener created
  2. TTriggerTemplate created
  3. TriggerBinding
  4. Interceptor created
  5. Ingress controller created and added into bitcukect webhook and also i can able to perform test connection (status code is 202) and also i have made two commits in bitbucket repos, i can able to Event log using repositoy page (successful calls 2/2 (100%))

Now the problem is pipeline not getting triggered if any changes happen in remote branch.

nvalid event body format : unexpected end of JSON input"}
{"severity":"error","timestamp":"2023-05-26T18:26:19.782Z","logger":"eventlistener","caller":"sink/validate_payload.go:42","message":"Invalid event body format : unexpected end of JSON input"}
{"severity":"error","timestamp":"2023-05-26T18:26:21.997Z","logger":"eventlistener","caller":"sink/validate_payload.go:42","message":"Invalid event body format : unexpected end of JSON input"}
{"severity":"error","timestamp":"2023-05-26T18:26:34.456Z","logger":"eventlistener","caller":"sink/validate_payload.go:42","message":"Invalid event body format : unexpected end of JSON input"}
{"severity":"error","timestamp":"2023-05-26T18:26:34.797Z","logger":"eventlistener","caller":"sink/validate_payload.go:42","message":"Invalid event body format : unexpected end of JSON input"
{"severity":"info","timestamp":"2023-05-27T12:40:50.103Z","logger":"eventlistener","caller":"sink/sink.go:418","message":"
interceptor stopped trigger processing: rpc error: code = InvalidArgument desc = no X-Hub-Signature header set","
eventlistener":"bitbucket-event-listener","namespace":"devops-cost-triggers","/triggers-eventid":"4262499e-5389-49f9-8593-4258aee73629",
"eventlistenerUID":"e36d7ea0-1e4d-4759-b4c7-49a1feb85cea","/triggers-eventid":"4262499e-5389-49f9-8593-4258aee73629","
/trigger":"bitbucket-trigger-binding"}
tekton-robot commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

tekton-robot commented 11 months ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

tekton-robot commented 10 months ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

tekton-robot commented 10 months ago

@tekton-robot: Closing this issue.

In response to [this](https://github.com/tektoncd/triggers/issues/1596#issuecomment-1777689839): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen` with a justification. >Mark the issue as fresh with `/remove-lifecycle rotten` with a justification. >If this issue should be exempted, mark the issue as frozen with `/lifecycle frozen` with a justification. > >/close > >Send feedback to [tektoncd/plumbing](https://github.com/tektoncd/plumbing). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.