Hi Oleg, The plugin developer/s are not to blame :) They surely do have the appropriate tests. Its just me, the thick user, jumping to conclusions.
Brg Arvid tors 8 juni 2017 kl 09:42 skrev Oleg Nenashev <[email protected]>: > No problem, it happens. > You may want to create a Jenkins ATH > <https://github.com/jenkinsci/acceptance-test-harness/> test to be sure > that Jenkins changes do not break your plugin logic. > > BR, Oleg > > среда, 7 июня 2017 г., 18:49:19 UTC+2 пользователь Arvid Huss написал: >> >> Hi, >> >> Sorry for the disturbance. It was entirely my fault, the webhook stoped >> working due to me misspelling the webhook URL. >> >> Sorry for any inconvenience. >> Arvid >> >> >> ons 7 juni 2017 kl 14:51 skrev Julien HENRY <[email protected]>: >> > >>> >>> Le mardi 6 juin 2017 21:56:33 UTC+2, Jesse Glick a écrit : >>> >>>> On Tue, Jun 6, 2017 at 1:27 PM, Arvid Huss <[email protected]> >>>> wrote: >>>> > I have already been in contact with the plugin developer and he >>>> refered me >>>> > to jenkins-dev mailing list. >>>> >>>> Well they will need to do some more evaluation on their end. >>>> >>> >>> Hi guys, >>> >>> I'm sorry if I missed something obvious, this is not my intention to >>> pass the buck, but the documentation >>> <https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes> >>> says: >>> >>>> There's a variant of this called UnprotectedRootAction >>>> <http://javadoc.jenkins-ci.org/byShortName/UnprotectedRootAction> that >>>> is made accessible even to anonymous users without the read access to >>>> Jenkins. >>> >>> Also we are doing a very similar implementation than what the Jenkins >>> GitHub plugin does. Finally I made a simple test (run Jenkins 2.64, enable >>> security, disable anonymous read) and everything looks fine. >>> >>> So if on Jenkins side you confirm there is no regression, my last guess >>> for this 403 error would be that there is an issue on your side Arvid. >>> Maybe you could try to temporarily enable anonymous read to see if that >>> bring back access to the <jenkins>/sonarqube-webhook/ URL. Also you can try >>> to access your Jenkins server without using the proxy (just to eliminate it >>> from the equation). >>> >>> ++ >>> >>> Julien >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/Vsa8f9r6mak/unsubscribe. >>> >> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/f4aec9f4-4f08-41b5-8bfe-9d124b6d944a%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/f4aec9f4-4f08-41b5-8bfe-9d124b6d944a%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/Vsa8f9r6mak/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/d61d56cf-7f20-4fca-9a46-34ac53e67742%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/d61d56cf-7f20-4fca-9a46-34ac53e67742%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC%3DtV8vkx68qJsYsXzmrjGzQ%3D_gFBB845jeJONe8HoL5SLLv-A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
