On Tue, Feb 18, 2014 at 4:47 PM, Andrew Bayer <[email protected]> wrote: > com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 500 Could not > initialize class org.kohsuke.stapler.Function$InstanceFunction for > http://localhost:59217/configure"; - that's with Jenkins core 1.509. But > everything works fine when I do mvn hpi:run
The test harness does not accurately mimic the class loader environment of Jenkins, unfortunately. (It does start up Jenkins with the full plugin class loader, but neglects to block loading of classes from the test classpath, which normally includes the tested plugin and all its dependencies.) Someone ambitious could look at something like NbTestSuite in NetBeans and try to do something analogous for Jenkins. > When I switch to 1.532, I get different errors - mvn hpi:run still works, > but now when the tests are running, they're getting 500s on attempts to hit > "configure" - i.e., via configRoundTrip(). Probably a stack trace is being printed to the Jenkins console when this happens, no? Check the test output. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
