In our case, we are using GitHub but we had similar concerns. Our solution was to create a little server with NGINX configured to forward the webhooks to our Jenkins masters. In this way, we could achieve the following: 1) Jenkins masters are not exposed at all to internet 2) The configuration are kept inside the server with NGINX (in your the token) 3) Changing the Jenkins master only require a change into the NGINX server and everything remains the same on GitHub
On Thursday, 19 March 2020 01:05:37 UTC, Jheison Rodriguez wrote: > > currently I'm using a webhooks token for trigger Jobs from GitLab to > Jenkins, I have a global user so a token set up for all project something > like this: https://USERID:APITOKEN@JENKINS_URL/project/YOUR_JOB > <https://USERID:APITOKEN@jenkins_url/project/YOUR_JOB> > > Additionally, when I create a new version of the Jenkins master the token > is updated and I need to update in each GitLab project. > > I'd like to know if someone has experienced this and had managed this kind > of set up in another way? Also to avoid expose the token in the webhooks' > URL (security concern) or update it (even with scripts) for each GitLab > project. > -- 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/f170fc2c-fabc-40f7-8f41-f8e804355f02%40googlegroups.com.
