-
Bug
-
Resolution: Fixed
-
Minor
-
None
Running version 1.1.3 of the kubernetes plugin on Jenkins 2.89.4.
We recently set up additional networking rules to the helm/kubernetes controlled elastic load balancer to only allow incoming connection from the IP addresses in our office.
After we made this change we discovered that jobs driven by Jenkinsfile were no longer being run automatically when a commit or PR was created on the GitHub side.
If I manually trigger a scan of the github project the job does run so I know it can successfully communicate with the github API but I'm wondering if the networking rules we put in place have had the effect screwing up the automatic triggers.