Why are builds not being triggered with Build Token Root Plugin? Félix Belzunce Arcos July 13, 2022 13:02 Updated The content of this article has moved to the new documentation site. Related articles How to Customize Checkout for Pipeline Multibranch? Navigation in Jenkins fails with 'No valid crumb was included in request' errors [CloudBees CI 2.277.1.2] Replace Acegi Security with Spring Security & upgrade Spring Framework Ingress Annotations missing during controller provisioning since 2.319.2.5 The remote end hung up unexpectedly while performing git checkout operation Comments 5 comments Sort by Date Votes Jesse Glick March 26, 2015 18:48 The plugin logs a detailed explanation at FINE of why it is ignoring a given request. 0 Douglas Ferguson May 02, 2015 18:24 It would be great to add this info the wiki. The examples on the wiki are incorrect and don't indicate that this needs to be a POST https://wiki.jenkins-ci.org/display/JENKINS/Build+Token+Root+Plugin 0 Jesse Glick May 04, 2015 11:43 POST is not required for this plugin (GET works too), and as far as I know the examples on the wiki are correct. 0 Douglas Ferguson May 04, 2015 14:06 Well.. I kept getting a 4xx until I found this article and changed it to a POST and escaped the & I did not try a get with the escaped &. I was also using a text editor to construct the command so I am confident that the only difference from my 2 commands are the POST and the & vs & 0 Jesse Glick May 04, 2015 15:02 Certainly if you are using a Unix shell to run curl, then you need to escape ampersands or otherwise quote the URL. That is not a mistake in the wiki examples, nor anything specific to Jenkins or this plugin, just additional clarification. 0 Please sign in to leave a comment.