smee-client icon indicating copy to clipboard operation
smee-client copied to clipboard

Requests are not coming on smee client

Open rnkhouse opened this issue 3 years ago • 2 comments

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).

rnkhouse avatar Mar 23 '21 18:03 rnkhouse

I see similar behaviour on our Jenkins (not running inside containers, though) and GitLab. It always starts working again after restarting Smee client. Version is 1.2.2. I've already setup a cron job to restart Smee client once every night, but that's not always sufficient.

dhs-rec avatar Oct 05 '21 05:10 dhs-rec

I think that this might be related to issue #179.

santiagob avatar Dec 01 '21 14:12 santiagob