Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18554

NPE in Maven Version slicer in 1.37

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • configurationslicing-plugin
    • None
    • Jenkins LTS 1.509.2
      Windows 7

      When I upgrade Configuration Slicing Plugin from 1.36 to 1.37 I get the attached NullPointerException when I click the following:

      1. Manage Jenkins
      2. Configuration Slicing
      3. Maven Version

      Downgrading to 1.36 makes the problem go away again.

        1. stacktrace.txt
          4 kB

          [JENKINS-18554] NPE in Maven Version slicer in 1.37

          Jacob Robertson added a comment -

          I can't reproduce. Do you have any special job types you're using that I can test against?

          Jacob Robertson added a comment - I can't reproduce. Do you have any special job types you're using that I can test against?

          Dennis Lundberg added a comment -

          Hi

          Here are some more details on my environment.

          Installed plugins apart from those who comes with Jenkins:

          • Static Analysis Utilities (totaling 7 plugins: base, Checkstyle, Duplicate Code Scanner, FindBugs, PMD, Task Scanner, Warnings)
          • Jenkins Maven Release Plugin Plugin

          I tried on a separate machine just to make sure, and I got the same error there.
          That installation only had two "Maven 2/3" jobs and no other jobs.
          Both are minimal projects with Subversion used as SCM.

          Verified it on both Jenkins LTS 1.509.1 and 1.509.2.

          Dennis Lundberg added a comment - Hi Here are some more details on my environment. Installed plugins apart from those who comes with Jenkins: Static Analysis Utilities (totaling 7 plugins: base, Checkstyle, Duplicate Code Scanner, FindBugs, PMD, Task Scanner, Warnings) Jenkins Maven Release Plugin Plugin I tried on a separate machine just to make sure, and I got the same error there. That installation only had two "Maven 2/3" jobs and no other jobs. Both are minimal projects with Subversion used as SCM. Verified it on both Jenkins LTS 1.509.1 and 1.509.2.

          Jacob Robertson added a comment -

          I've looked at this, and it looks pretty clear that the code changes made by Nicolas De Loof from CloudBees causes this. The plugin wasn't designed to handle "getAllItems", and that code change was made without enough testing. I have assigned the ticket to him.

          Jacob Robertson added a comment - I've looked at this, and it looks pretty clear that the code changes made by Nicolas De Loof from CloudBees causes this. The plugin wasn't designed to handle "getAllItems", and that code change was made without enough testing. I have assigned the ticket to him.

            ndeloof Nicolas De Loof
            dennisl Dennis Lundberg
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: