• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • matrix-project-plugin
    • None
    • CentOS 6.2

      No matrix jobs get loaded with Jenkins 1.473. The jobs and any related information is missing. The log shows the following backtrace:

      Jul 2, 2012 11:14:34 AM jenkins.InitReactorRunner$1 onTaskFailed
      SEVERE: Failed Loading job Test matrix
      java.lang.NullPointerException
      	at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431)
      	at hudson.model.AbstractProject.onLoad(AbstractProject.java:296)
      	at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466)
      	at hudson.model.Items.load(Items.java:115)
      	at jenkins.model.Jenkins$17.run(Jenkins.java:2492)
      	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
      	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
      	at jenkins.model.Jenkins$7.runTask(Jenkins.java:878)
      	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
      	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
      	at java.lang.Thread.run(Thread.java:679)
      

          [JENKINS-14273] Matrix jobs don't get loaded

          Marking as fixed in 1.475

          Richard Mortimer added a comment - Marking as fixed in 1.475

          Ido Ran added a comment -

          Version 1.475 is not release yet. How can I workaround this issue?

          Ido Ran added a comment - Version 1.475 is not release yet. How can I workaround this issue?

          erwan_q added a comment -

          Downgrading back to 1.472 fixes.

          erwan_q added a comment - Downgrading back to 1.472 fixes.

          I'm wondering why this important bugfix didn't become part of the recently released Jenkins v1.474 but is intended for a not-yet-available/to-be-released version only?

          Michael Prokop added a comment - I'm wondering why this important bugfix didn't become part of the recently released Jenkins v1.474 but is intended for a not-yet-available/to-be-released version only?

          Thomas Fields added a comment -

          I'd love to know the reasoning behind that as well. It's obviously so important we get the French translation correct!

          Thomas Fields added a comment - I'd love to know the reasoning behind that as well. It's obviously so important we get the French translation correct!

          I don't follow the ins and outs of the release process that closely but basically v1.474 had already been built by the time that this issue was reported/fixed.

          The weekly builds are basically just snapshots of the current state of the tree at the time of the build. They allow the latest changes to get to a wider audience and to catch bugs like this before they get into a long-term release. There is always scope for better unit/integration testing and help is appreciated.

          If you need a known/stable build then I would suggest that you switch to the LTS release that is updated every 3 months or so after more extensive testing.

          Richard Mortimer added a comment - I don't follow the ins and outs of the release process that closely but basically v1.474 had already been built by the time that this issue was reported/fixed. The weekly builds are basically just snapshots of the current state of the tree at the time of the build. They allow the latest changes to get to a wider audience and to catch bugs like this before they get into a long-term release. There is always scope for better unit/integration testing and help is appreciated. If you need a known/stable build then I would suggest that you switch to the LTS release that is updated every 3 months or so after more extensive testing.

          Randall Hunt added a comment -

          Can't believe this made it into a release and out to package managers, awful bug.

          Randall Hunt added a comment - Can't believe this made it into a release and out to package managers, awful bug.

          Jim Searle added a comment -

          Is this fix in Jenkins 1.475? I don't see it in the changelog yet.

          Jim Searle added a comment - Is this fix in Jenkins 1.475? I don't see it in the changelog yet.

          Yes, it works for me again with Jenkins 1.475.

          Michael Prokop added a comment - Yes, it works for me again with Jenkins 1.475.

          Didn't work in 1.473, but works for me in 1.475 as well. Seems like it is fixed but not marked with the proper fix version?

          David Humeniuk added a comment - Didn't work in 1.473, but works for me in 1.475 as well. Seems like it is fixed but not marked with the proper fix version?

            Unassigned Unassigned
            desolat Christoph Jaehnigen
            Votes:
            6 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: