Requests are not coming on smee client

rnkhouse commented 3 years ago

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

dhs-rec commented 3 years ago

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.

santiagob commented 2 years ago

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

probot / smee-client

Requests are not coming on smee client #163