Awesome! So I could run the smee client on a separate physical host, but with network connectivity to my Jenkins server. Both the smee client and the Jenkins server would be behind the firewall.
To be cool, I could Dockerize the smee client, and deploy that in my Kubernetes cluster. However, I want to understand how the pieces fit together before I do that. One other question, which organization is behind https://smee.io/ ? If I do a whois lookup, I see: Registrant Organization: GitHub, Inc. Is this a fully supported service of GitHub, or a side project? I don't want to try using a service which may disappear..... -- Craig On Thu, Oct 24, 2019 at 2:39 PM Michael Neale <mne...@cloudbees.com> wrote: > yeah fair point it doesn't have to be right next to it - but it has to be > somewhere it can reach /github-webhook endpoint - so could be a totally > separate app? (as long as your Jenkins master instance is discoverable and > accessible from elsewhere from the cluster - which I guess it would be > right?). It only uses the REST api, and only the /github-webhook endpoint, > nothing else. > > On Fri, Oct 25, 2019 at 1:18 AM Craig Rodrigues <rodr...@crodrigues.org> > wrote: > >> This seems unnecessarily complicated. >> Why does the smee client need to be next to the Jenkins server at all? >> >> If I was not using Kubernetes, and if I had two separate physical >> machines, >> one running Jenkins and one running smee, >> would it be possible for smee to interact with Jenkins via the REST API? >> >> -- >> Craig >> >> On Thu, Oct 24, 2019 at 1:01 AM Michael Neale <mne...@cloudbees.com> >> wrote: >> >>> Hi Craig, glad that post is getting mileage! >>> >>> So in kubernetes, I guess that would be adding to the pod that is >>> running your Jenkins container: there would be a pod definition (not sure >>> if you wrote it) somewhere, and you could cook up an image with smee >>> running and have it as a "sidecar" next to the Jenkins container, as pods >>> share a network and anything running in the pod could access the >>> /github-webhook/ endpoint >>> >>> https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look >>> for sidecar) >>> >>> So then it depends how you deployed that image into a pod (but to start >>> with would need to cook up an image with smee in it ready to go - I am not >>> sure if one exists yet). >>> >>> >>> >>> On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues <rodr...@crodrigues.org> >>> wrote: >>> >>>> Michael, >>>> >>>> In your blog post: >>>> >>>> "Triggering builds with webhooks behind a secure firewall" >>>> https://jenkins.io/blog/2019/01/07/webhook-firewalls/ >>>> >>>> You gave a good overview of how someone can use webhooks >>>> invoked from GitHub in the cloud, to a Jenkins server which exists >>>> behind >>>> a firewall, using https://smee.io . >>>> >>>> In your post, you mention: >>>> >>>> *"you should install the smee client next to where you have the Jenkins >>>> server running:*" >>>> >>>> In my case, I am running the jenkins/jenkins:lts docker image >>>> ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by >>>> Kubernetes 1.14. >>>> My Jenkins setup is behind a firewall. >>>> However, my source code exists on GitHub which exists in the public >>>> cloud. >>>> >>>> Since I do not want to modify the jenkins/jenkins:lts docker image, >>>> where can I run the smee client, so that I can still use it >>>> with my setup? >>>> >>>> I'd like to get webhooks from the public GitHub triggering builds on >>>> my Jenkins server running behind a firewall. >>>> >>>> Thanks. >>>> >>>> -- >>>> Craig >>>> >>> >>> >>> > > -- 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/CAG%3DrPVeqUdpJUCzecSyb%2BHmLO4X2hGkCzaNWRnbS8Y9oDP%2B2sA%40mail.gmail.com.
