Actually something's not quite right. Firstly, the configuration in the Multibranch project to "Trigger builds remotely" disappears after I save. Select the option, put a token, save and reopen. They are gone.
Secondly, assuming the configuration is actually saved, the url to trigger the build needs to have the branch name in it: <jenkins_url>/job/<job name>/branch/master/build?token=some token This actually works (despite the config seemingly not being saved). But without the branch name in the url it doesn't do anything. So do I have to setup a different webhook for each branch? It feels like this should work out of the box and I'm doing something very silly. And yet, invoking the url with curl triggers the build. Seems like a UI problem. On Saturday, 7 May 2016 12:29:22 UTC+10, Lionel Orellana wrote: > > Hi All > > How can I trigger a build on a multibranch pipeline where there is a push > in github and Jenkins requires authentication. > > I tried "Trigger builds remotely (e.g., from scripts)" but the token > generated here isn't enough for a github webhook to authenticate with > Jenkins. Github throws "Authentication required". This is using a > webhook like <jenkins_url>/job/<job name>/build?token=some token where > the token matches what's in the "Trigger builds remotely" configuration. > > Thanks > > Lionel. > > > -- 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/78ab11b0-4df2-47a2-8153-a2c51ab1fc7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
