Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requests are not coming on smee client #163

Open
rnkhouse opened this issue Mar 23, 2021 · 2 comments
Open

Requests are not coming on smee client #163

rnkhouse opened this issue Mar 23, 2021 · 2 comments

Comments

@rnkhouse
Copy link

rnkhouse commented Mar 23, 2021

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 rnkhouse changed the title Requests are not coming on internal server Requests are not coming on smee client Mar 23, 2021
@dhs-rec
Copy link

dhs-rec commented Oct 5, 2021

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants