-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Version 2.426.2
Bitbucket Branch Source Version 856.v04c46c86f911
We have a Jenkins deployment running behind an AWS LB, receiving 443, then forwarding 8080 to jenkins.
Webhook is
https://build.xxx.com/bitbucket-scmsource-hook/notify |
Whenever there's a PR created on Bitbucket Cloud, the build is marked as success without issues. After a given set of hours, say 10, the build status is regenerated as failed, alongside with a new webhook showing an 8080 and http.
I've enabled access logs in Jenkins, access logs in the LB, Webhook logs, and I can't find any trace on the jenkins server adding this webhook to bitbucket, so where is this coming from? I also can't find any traces of jenkins updating the redirects on the builds, but there is log about the first success, so I'm baffled at this point
There used to be an NGINX but that's not running anymore, and there's no 8080 anywhere.