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

NullPointerException in release plugin if maven decides the version

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • m2release-plugin
    • None
    • Linux/jenkins 1.414 stand-alone (not in tomcat)/release plugin 0.7.1

      If we allow maven to decide the version number for a release (which generally is what we want to do) then we get the following exception invariably across all our projects:
      ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
      java.lang.NullPointerException
      at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getReleaseVersion(M2ReleaseBuildWrapper.java:336)
      at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.setUp(M2ReleaseBuildWrapper.java:159)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:607)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429)
      at hudson.model.Run.run(Run.java:1375)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)

      The workaround is to click on the radio button "Specify one version for all modules". The default values there are fine.

          [JENKINS-9888] NullPointerException in release plugin if maven decides the version

          Peter Hayes added a comment -

          reassigning to M2 release plugin

          Peter Hayes added a comment - reassigning to M2 release plugin

          scooper4711 added a comment -

          The workaround isn't working for all projects. For some projects, we get this regardless of letting maven decide, specifying one version for all modules or setting the version name separately for each module.

          scooper4711 added a comment - The workaround isn't working for all projects. For some projects, we get this regardless of letting maven decide, specifying one version for all modules or setting the version name separately for each module.

          James Nord added a comment -

          does this still occur with 0.8.0?

          James Nord added a comment - does this still occur with 0.8.0?

          scooper4711 added a comment -

          We were just encountering this bug again for a project, and decided to upgrade from 0.7.1 to 0.8 because of your question.
          With a single data-point I can say that the 0.8.0 upgrade solved the issue.

          I suggest that you close this issue, and if it re-occurs then I'll request that you re-open it for us.

          Thanks!
          Stephen

          scooper4711 added a comment - We were just encountering this bug again for a project, and decided to upgrade from 0.7.1 to 0.8 because of your question. With a single data-point I can say that the 0.8.0 upgrade solved the issue. I suggest that you close this issue, and if it re-occurs then I'll request that you re-open it for us. Thanks! Stephen

          James Nord added a comment -

          as per above comment

          James Nord added a comment - as per above comment

            Unassigned Unassigned
            scooper4711 scooper4711
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: