-
Notifications
You must be signed in to change notification settings - Fork 157
Open
Description
I am using smee URL to trigger push events from bitbucket to Jenkins. Using smee client in Jenkins as sidecar conteiner. Please check below code:
- name: smee-bitbucket
image: docker.io/oveits/smee-client:latest
args: ["--port", "{{ .Values.controller.servicePort }}", "--path", "/bitbucket-scmsource-hook/notify/", "--url", "https://smee.io/<test>"]
resources:
limits:
cpu: 50m
memory: 128Mi
requests:
cpu: 10m
memory: 32Mi
env:
- name: NODE_TLS_REJECT_UNAUTHORIZED
value: "0"
When I commit-push on bitbucket it creates a request to the provided webhook endpoint. I also checked on smee.io and I see the request with payload. Somehow, this request is not coming in smee-client.
It was working fine before. Suddenly, stopped working not sure why. How can I debug this?
PS: Sometimes, when I deploy the fresh Jenkins server it works (I see the logs on smee client) for few requests and stops working again (don't see new requests coming in).
Metadata
Metadata
Assignees
Labels
No labels