All of the Qpid jobs are exhibiting this problem. A lot of them are also throwing checksum exceptions during their SVN updates which I was hoping to fix by setting the jobs to do a fresh checkout and running them on the various nodes they use, but I can't currently configure them due to this problem.
Robbie On 27 June 2012 20:52, Olivier Lamy <ol...@apache.org> wrote: > Hi, > Which job are you editing ? > Maybe it's only one plugin which need some upgrade (but not sure about > whole jenkins instance) > > Cheers, > -- > Olivier > > 2012/6/27 giridharan kesavan <gkesa...@hortonworks.com>: >> All, >> >> It looks like the recent upgrades of jenkis is broken. >> clicking on job configuration of any job show up the following trace >> >> >> Status Code: 500 >> >> Exception: org.apache.commons.jelly.JellyTagException: >> file:/home/hudson/hudson/plugins/promoted-builds/WEB-INF/classes/hudson/plugins/promoted_builds/JobPropertyImpl/config.jelly:5:79: >> <st:include> Error setting property 'class', exception - >> org.apache.commons.beanutils.ConversionException: No value specified for >> 'Class' >> Stacktrace: >> >> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: >> file:/home/hudson/hudson/plugins/promoted-builds/WEB-INF/classes/hudson/plugins/promoted_builds/JobPropertyImpl/config.jelly:5:79: >> <st:include> Error setting property 'class', exception - >> org.apache.commons.beanutils.ConversionException: No value specified for >> 'Class' >> at >> org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) >> >> >> Is anyone aware of a way to fix this? >> >> If not then I'm going to downgrade jenkins to the previous version. >> >> >> >> -- >> -Giri >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy
