On Friday, December 2, 2022 at 8:52:26 AM UTC-7 Madhu Muchukota wrote:
> Hi Team, > > We recently upgraded Jenkins and as a part of this, plugins too got > upgraded. > > We use Service Hooks in Azure DevOps and after the upgrade, we are seeing > GIT notifyCommit is failing with HTTP status code 401. > > Upon troubleshooting, I came to know that the Jenkins Git Plugin that got > upgraded to the latest version needs notifyCommit token and I don't have > any option to pass that notifyCommit token on my Azure DevOps service hook > subscription page. > > Did anyone run into the same issue? and is there any property through > which I can disable this notifyCommit token option? > > The git plugin documentation <https://plugins.jenkins.io/git/#plugin-content-push-notification-from-repository> says The token parameter is required by default as a security measure, but can be disabled by the following system property <https://www.jenkins.io/doc/book/managing/system-properties/>: hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL It has two modes: - disabled-for-polling - Allows unauthenticated requests as long as they only request polling of the repository supplied in the url query parameter. Prohibits unauthenticated requests that attempt to schedule a build immediately by providing a sha1 query parameter. - disabled - Fully disables the access token mechanism and allows all requests to notifyCommit to be unauthenticated. *This option is insecure and is not recommended.* -- 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/34f1422f-8df5-48a7-91b8-52a99a96a25fn%40googlegroups.com.
