• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None
    • Slave on Windows 7 64-bit, Master on Solaris 10. Jenkins version 1.436.

      Getting this at the start of the build. Its reporting FAILURE building the parent module (aggregated poms) this is after upgrading from Jenkins 1.432 to 1.436. Reverting back to 1.432 problem goes away.

      Config is a M3 project I've tried 1 or more threads with same result.

      15:04:36 mavenExecutionResult exceptions not empty
      15:04:36 message : Internal error: java.lang.NullPointerException
      15:04:36 cause : null
      15:04:36 Stack trace :
      15:04:36 org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
      15:04:36 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
      15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
      15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
      15:04:36 at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
      15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      15:04:36 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      15:04:36 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      15:04:36 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      15:04:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      15:04:36 at java.lang.Thread.run(Thread.java:662)
      15:04:36 Caused by: java.lang.NullPointerException
      15:04:36 at hudson.maven.AbstractMavenBuilder$FilterImpl.executeAsync(AbstractMavenBuilder.java:174)
      15:04:36 at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:128)
      15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectSucceeded(Maven3Builder.java:378)
      15:04:36 at hudson.maven.Maven3Builder$MavenExecutionListener.projectSucceeded(Maven3Builder.java:352)
      15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74)
      15:04:36 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      15:04:36 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91)
      15:04:36 ... 10 more

          [JENKINS-11458] NPE running Maven 3 job

          banoss created issue -
          kutzi made changes -
          Assignee New: kutzi [ kutzi ]

          kutzi added a comment -

          Ouch

          kutzi added a comment - Ouch

          kutzi added a comment -

          The build does happen on master or on a slave?

          kutzi added a comment - The build does happen on master or on a slave?

          banoss added a comment -

          Sorry, build is on slave. Deleted slave files and restarted when I upgraded Jenkins to ensure latest versions were copied. checked slave logs which look fine - no errors.

          <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.11
          This is a Windows slave
          Copied maven-agent.jar
          Copied maven3-agent.jar
          Copied maven3-interceptor.jar
          Copied maven-interceptor.jar
          Copied maven2.1-interceptor.jar
          Copied plexus-classworld.jar
          Copied classworlds.jar
          Slave successfully connected and online

          Also just tried running job on the (unix) master - same result.

          Tried much simpler job similar config (ie parent pom and 3 modules) but that works fine...

          banoss added a comment - Sorry, build is on slave. Deleted slave files and restarted when I upgraded Jenkins to ensure latest versions were copied. checked slave logs which look fine - no errors. <=== [JENKINS REMOTING CAPACITY] ===>Slave.jar version: 2.11 This is a Windows slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online Also just tried running job on the (unix) master - same result. Tried much simpler job similar config (ie parent pom and 3 modules) but that works fine...

          kutzi added a comment -

          So the obvious question is: can you track down the differences of the projects which trigger the failure?

          kutzi added a comment - So the obvious question is: can you track down the differences of the projects which trigger the failure?

          banoss added a comment -

          The one that fails is a much larger project (80 components - pom structure is 6 levels deep) the smaller test project is only 4 components - parent and 1 level of children.

          The more interesting question is why can i up/downgrade between 1.436/1.432 and it builds fine on 1.432 but always fails on 1.436!

          I will try versions of Jenkins in between and see where it starts to fail.

          banoss added a comment - The one that fails is a much larger project (80 components - pom structure is 6 levels deep) the smaller test project is only 4 components - parent and 1 level of children. The more interesting question is why can i up/downgrade between 1.436/1.432 and it builds fine on 1.432 but always fails on 1.436! I will try versions of Jenkins in between and see where it starts to fail.

          kutzi added a comment -

          Try 1.434 and 1.435 first! I guess that it's was introduced in 1.435. Also, it should be enough to change the maven-plugin

          kutzi added a comment - Try 1.434 and 1.435 first! I guess that it's was introduced in 1.435. Also, it should be enough to change the maven-plugin

          banoss added a comment -

          Ahh Kutzi, correct as always. 1.434 works fine; 1.435 is when this issue starts to occur.

          banoss added a comment - Ahh Kutzi, correct as always. 1.434 works fine; 1.435 is when this issue starts to occur.

          Code changed in jenkins
          User: Christoph Kutzinski
          Path:
          maven-plugin/src/main/java/hudson/maven/AbstractMavenBuilder.java
          maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
          http://jenkins-ci.org/commit/jenkins/609b321e6ee0963908dddda048d572f2550e75aa
          Log:
          JENKINS-11458 when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Christoph Kutzinski Path: maven-plugin/src/main/java/hudson/maven/AbstractMavenBuilder.java maven-plugin/src/main/java/hudson/maven/Maven3Builder.java http://jenkins-ci.org/commit/jenkins/609b321e6ee0963908dddda048d572f2550e75aa Log: JENKINS-11458 when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.

            kutzi kutzi
            banoss banoss
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: