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

Default value of Maven2 build password parameter doesn't get persisted

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: PC, OS: Linux

      Password parameter default value one enters seems not to be persisted, so jobs
      which are triggered automatically or run manually without user setting password
      parameter value, fail with the NPE exception (see [1]). When Hudson
      (MavenBuilder) tries to set/put all system properties back to the system
      including a null value I suppose for that password parameter, since system
      properties are held in a Hashtable which doesn't support null values, we got a NPE.

      [1] build job execution stack trace snippet

      ERROR: Processing failed due to a bug in the code. Please report this to
      users@hudson.dev.java.net
      java.lang.NullPointerException
      at java.util.Hashtable.put(Hashtable.java:394)
      at java.util.Hashtable.putAll(Hashtable.java:466)
      at hudson.maven.MavenBuilder.call(MavenBuilder.java:156)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:685)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:631)
      at hudson.remoting.UserRequest.perform(UserRequest.java:103)
      at hudson.remoting.UserRequest.perform(UserRequest.java:47)
      at hudson.remoting.Request$2.run(Request.java:236)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)

          [JENKINS-4352] Default value of Maven2 build password parameter doesn't get persisted

          Stevo Slavić added a comment -

          Seems to be fixed in Hudson ver. 1.327

          Stevo Slavić added a comment - Seems to be fixed in Hudson ver. 1.327

          After upgrading to hudson 1.353 (and the latest git plugin version) I got the following on the next build:

          channel stopped
          ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net
          java.lang.NullPointerException
          at java.util.Hashtable.put(Hashtable.java:394)
          at java.util.Hashtable.putAll(Hashtable.java:466)
          at hudson.maven.MavenBuilder.call(MavenBuilder.java:156)
          at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688)
          at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632)
          at hudson.remoting.UserRequest.perform(UserRequest.java:114)
          at hudson.remoting.UserRequest.perform(UserRequest.java:48)
          at hudson.remoting.Request$2.run(Request.java:270)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
          at java.util.concurrent.FutureTask.run(FutureTask.java:138)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)

          Looking at the environment I see:

          Env: GIT_BRANCH=null

          Apparently in the git configuration for the build the default value of empty string for the branch config is no longer acceptable. This then also causes a crash in the maven build due to the the null value.

          matthewnewhook added a comment - After upgrading to hudson 1.353 (and the latest git plugin version) I got the following on the next build: channel stopped ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at java.util.Hashtable.putAll(Hashtable.java:466) at hudson.maven.MavenBuilder.call(MavenBuilder.java:156) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Looking at the environment I see: Env: GIT_BRANCH=null Apparently in the git configuration for the build the default value of empty string for the branch config is no longer acceptable. This then also causes a crash in the maven build due to the the null value.

          Stevo Slavić added a comment -

          It seems this issue is duplicate of JENKINS-4333

          Stevo Slavić added a comment - It seems this issue is duplicate of JENKINS-4333

          evernat added a comment -

          yes, it is certainly a duplicate of JENKINS-4333, which is fixed

          evernat added a comment - yes, it is certainly a duplicate of JENKINS-4333 , which is fixed

            Unassigned Unassigned
            sslavic Stevo Slavić
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: