The same thing happens with the Build Token Root Plugin (XXXXX is used instead of the real server DNS):
curl -X POST http://XXXXX:8915/jenkins/job/build-entity-service/buildByToken/build?token=gmasbuild I'm running with Tomcat 7.0.47, so I also made sure that URI encoding is UTF-8 (I don't get a warning in the Jenkins console anymore.) Something else is wrong. Should I try running with a different container or installing the latest version? On Tuesday, September 15, 2015 at 1:30:03 PM UTC-4, John Marks wrote: > > I'm using the following linux command line to do a remote build using > Jenkins version 1.613 > > curl -X POST > http://gmastst-app2.cadm.harvard.edu:8915/jenkins/job/build-gmas-entity-service/build > > --data token=gmasbuild > > What I get looks like a long HTML response that's expecting a log in > followed by a stack trace which says it can't find method > java.net.URLEncoder.encode(). > > A similar command line (host, build name and token differ) run against > version 1.541 works flawlessly. I've tried the above using both Java 1.7. > and 1.8 with the same result. > > Can someone help me figure out what might be wrong? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/59aae083-6995-4cb5-9c74-ad669314b8b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
