You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkins.rb
I've made a couple changes to the ruby-runtime plugin to look in the
script dir for bundled gems, and also to the rake task to actually
bundle the gems and put them in the place where RubyPlugin will look
for them.
However, I'm having trouble testing because, I'm not able actually
load the 1.427-SNAPSHOT server warfile. in order to test it. I keep
getting this error from the built jar.
legolas:jenkins-prototype-ruby-plugin cowboyd$ ls work/plugins/
ruby-prototype.hpi ruby-runtime.hpi
legolas:jenkins-prototype-ruby-plugin cowboyd$ java -
DJENKINS_HOME=work -jar jenkins.war
Running from: /Users/cowboyd/Projects/Jenkins/jenkins-prototype-ruby-
plugin/jenkins.war
webroot: System.getProperty("JENKINS_HOME")
Exception in thread "main" java.lang.IllegalAccessException: Can not
set static final java.lang.String field
winstone.WinstoneSession.SESSION_COOKIE_NAME to java.lang.String
at
sun.reflect.UnsafeFieldAccessorImpl.throwFinalFieldIllegalAccessException(UnsafeFieldAccessorImpl.java:
55)
at
sun.reflect.UnsafeFieldAccessorImpl.throwFinalFieldIllegalAccessException(UnsafeFieldAccessorImpl.java:
59)
at
sun.reflect.UnsafeQualifiedStaticObjectFieldAccessorImpl.set(UnsafeQualifiedStaticObjectFieldAccessorImpl.java:
59)
at java.lang.reflect.Field.set(Field.java:657)
at Main._main(Main.java:265)
at Main.main(Main.java:96)
thoughts?
cheers,
Charles
Kohsuke Kawaguchi
unread,
Aug 19, 2011, 9:24:26 AM8/19/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenk...@googlegroups.com, Charles Lowell
For the record, we've fixed this during the hack session. This was caused by the botched 0.9.10-jenkins-26 release where I ended up releasing two binaries under one name.
Bumping up to 0.9.10-jenkins-27 did the trick (so is using released 1.426 version)
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins