Hello, I've got a question and a possible answer but since I'm new to Jenkins and it's plugins maybe there is an easier way to do the thing I'm trying to accomplish.
First of my current setup is the following: - Gitlab hosted on a server - Jenkins on premise with dynamic IP and hard to open up a port Since I understood by now that polling is a CI anti-pattern I'd very much like to use webhooks to trigger Jenkins builds but of course I won't be able to set this up with webhook posting to localhost. So I've thought of posting to an intermediary script (eg. node.js) running on a external server with static IP which would receive all of the webhooks and which Jenkins would be connected to with a client via a socket for example, effectively waiting for incoming data. Upon new data it would trigger new Jenkins job locally, expectedly immediately after the intermediary receives the payload. I know it's a bit odd way around but opening up a port is a bigger difficulty in my setup than actually deploying the above. Also hosting Jenkins on the mentioned server is not an option for me as I want to run builds and tests on actual hardware in some cases. So my question would be if maybe there is some already existing solution for this? Initially I've tried with DDNS but it didn't do the job unfortunately. I've been looking for topics from people with similar experiences but haven't found anything. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/75b88d8e-fdd4-4f21-a154-d4ce5e4e5d79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
