Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
CentOS 6.3
JDK 1.6.0_37-b06
Description
After upgrading to version 1.522, some jobs were not correctly loaded once restarting jenkins. The following error is shown for some jobs in the jenkins log while restarting:
Jul 9, 2013 10:15:55 AM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job Base-Checkout.Install
java.lang.NoSuchFieldError: triggers
at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187)
Not sure which specific configuration inside that jobs cause the problem but once jenkins is started the jobs are not listed nor located by other jobs that depend on them
Attachments
Issue Links
- depends on
-
JENKINS-19383 Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers
-
- Resolved
-
-
JENKINS-21579 Very slow resource loading from UberClassLoader
-
- Resolved
-
- is blocking
-
JENKINS-18589 Deadlock
-
- Resolved
-
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
core/src/main/java/hudson/ClassicPluginStrategy.java
core/src/main/java/hudson/PluginManager.java
core/src/main/java/hudson/model/AbstractProject.java
pom.xml
http://jenkins-ci.org/commit/jenkins/47de54d070f67af95b4fefb6d006a72bb31a5cb8
Log:
[FIXED JENKINS-18677]
Integrated bytecode-compatibility-transformer that allows core to
do signature changes on properties that plugins might depend on.
The library performs necessary bytecode transformation to achieve this.
The first use of this is to fix plugins that looks for List
AbstractProject.triggers, thereby resolving
JENKINS-18677.For the time being, I'm not loading such compatibility annotations from
plugins, but I did code that in PluginManager. Let's see how this
feature work out for a while in the core, and if it looks stable and
solid, we'll open it up to plugins at that point.
Compare: https://github.com/jenkinsci/jenkins/compare/2135a17552fd...47de54d070f6