You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
rnkhouse
changed the title
Requests are not coming on internal server
Requests are not coming on smee client
Mar 23, 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.
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:
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).
The text was updated successfully, but these errors were encountered: