[JIRA] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Jan Mnisi
updated JENKINS-15841
tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Change By:
Jan Mnisi
(19/Nov/12 4:29 PM)
Description:
Hi.We get the following error running tests on Jenkins.{noformat}Xvfb starting$ Xvfb :1 -screen 0 1152x900x8 -fbdir /home/tomcat/.hudson/2012-11-16_11-25-053509576821944113109xvfbParsing POMsXvfb stoppingFATAL: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpljava.lang.IllegalAccessError: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpl at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:646) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1516) at hudson.model.Run.run(Run.java:1462) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:487) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236){noformat}Here is our set-up. Jenkins version: 1.490The Jenkins.war was renamed to Hudson.war and overwrote the Hudson.war one we had within tomcat. That allowed is to retain all the jobs we have now, including the ones that we build with maven but have no screens/windows.We also have XVFB installed on the master, which is a RHL 4 box (Nahant).And we use the latest XVFB plugin, VERSION 1.0.6 (NoV 05, 2012, required core dependencies = 1.398)The tests are Webdriver Java tests. Maven is used for building. The Pom gives no issues when we run tests locally. Below is what we have in the Pom, very few dependencies.{code}4.0.0ourGroupIdourArtifactId1jarorg.apache.maven.pluginsmaven-compiler-plugin2.5.11.71.7maven-failsafe-plugin2.12.3integration-testverifypertesttruejunitjunit4.10jarcompileorg.seleniumhq.seleniumselenium-java2.25.0org.easytestingfest-assert1.4testcom.intellijannotations9.0.4joda-timejoda-time2.1org.seleniumhq.seleniumselenium-server2.25.0jarcompile org.seleniumhq.selenium selenium-remote-driver 2.25.0 jar compile {code}
I am running Maven 3.0.4, and that's what I have in the path.
Please help.Jan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Jan Mnisi commented on JENKINS-15841 tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V This is what I saw whilst trying to understand the error and look for a workaround/fix... setBuiltOnStr protected void setBuiltOnStr(String builtOn) Allows subtypes to set the value of builtOn. This is used for those implementations where an AbstractBuild is made 'built' without actually running its run() method. Since: 1.429 I do understand that AbstractBuild is the base implementation of Run, but then I don't quite get why this is just being made "built" without running the run method. That seems to be the issue here, and I have no way to bypass this when running on Jenkins. Would a pure jenkins installation handle this better than a one-time Hudson installation that was updated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Jan Mnisi created JENKINS-15841 tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V Issue Type: Bug Affects Versions: current Assignee: bap Components: any-buildstep Created: 16/Nov/12 11:39 AM Description: Hi. We get the following error running tests on Jenkins. Xvfb starting$ Xvfb :1 -screen 0 1152x900x8 -fbdir /home/tomcat/.hudson/2012-11-16_11-25-053509576821944113109xvfb Parsing POMs Xvfb stopping FATAL: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpl java.lang.IllegalAccessError: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpl at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:646) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1516) at hudson.model.Run.run(Run.java:1462) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:487) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Here is our set-up. Jenkins version: 1.490 The Jenkins.war was renamed to Hudson.war and overwrote the Hudson.war one we had within tomcat. That allowed is to retain all the jobs we have now, including the ones that we build with maven but have no screens/windows. We also have XVFB installed on the master, which is a RHL 4 box (Nahant). And we use the latest XVFB plugin, VERSION 1.0.6 (NoV 05, 2012, required core dependencies = 1.398) The tests are Webdriver Java tests. Maven is used for building. The Pom gives no issues when we run tests locally. Below is what we have in the Pom, very few dependencies. 4.0.0 ourGroupId ourArtifactId 1 jar org.apache.maven.plugins maven-compiler-plugin 2.5.1 1.7 1.7 maven-failsafe-plugin 2.12.3 integration-test verify pertest true junit junit 4.10 jar compile org.seleniumhq.selenium selenium-java 2.25.0 org.easytesting fest-assert 1.4 test com.intellij annotations 9.0.4 joda-time joda-time 2.1 org.seleniumhq.selenium selenium-server 2.25.0 jar compile org.seleniumhq.selenium selenium-remote-driver 2.25.0 jar compile Please help. Jan Project: Jenkins Priority: Major Reporter: Jan Mnisi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/softwa
