[JIRA] Created: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
-------------------------------------------------------------------------------------------------------

                 Key: HUDSON-6429
                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
             Project: Hudson
          Issue Type: Bug
          Components: maven2
         Environment: Hudson 1.351, Maven 2.2.1
            Reporter: kutzi
            Priority: Critical


I've got this exception while running the build:

ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
java.lang.NullPointerException
        at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
        at hudson.model.Run.run(Run.java:1240)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:122)


This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?

I've also a Maven job with incremental build option.
The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.

Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138347#action_138347 ]

vlatombe commented on HUDSON-6429:
----------------------------------

I'm having a similar problem with Hudson 1.356
java.lang.NullPointerException
                 at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:435)
                 at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
                 at hudson.model.Run.run(Run.java:1244)
                 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
                 at hudson.model.ResourceController.execute(ResourceController.java:88)
                 at hudson.model.Executor.run(Executor.java:122)

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138348#action_138348 ]

vlatombe commented on HUDSON-6429:
----------------------------------

I just runned the incriminating job once again, and it seems to be due to a duplicated module.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138349#action_138349 ]

kutzi commented on HUDSON-6429:
-------------------------------

As far as I can reconstruct it, no duplicate module has been involved in my case.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kutzi reassigned HUDSON-6429:
-----------------------------

    Assignee: abayer

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

abayer reassigned HUDSON-6429:
------------------------------

    Assignee:     (was: abayer)

I'm not sure if I'm going to have time to look into this for a while due to work - check with Kohsuke to see if he can take a look.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138365#action_138365 ]

kutzi commented on HUDSON-6429:
-------------------------------

Strange. I did a view on the source code and it looks to me pretty much impossible that a NPE is happening there.

The line 432 resp. 435 is
if ((mb.getPreviousBuiltBuild() == null) ||

while mb is instantiated some lines earlier with
MavenBuild mb = m.newBuild();

And it looks like newBuild() can never return null

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138500#action_138500 ]

kutzi commented on HUDSON-6429:
-------------------------------

I just had the exact same problem again. Again, the previous build was aborted manually, so that seems to be the cause (there were no aborted builds in the mean time).
Starting the full build by manually triggering the job, fixed it again.


> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138502#action_138502 ]

kutzi commented on HUDSON-6429:
-------------------------------

I think this could be the offending line:

|| (mb.getPreviousBuiltBuild().getResult().isWorseThan(Result.SUCCESS)))

I've seen before that a build Result could be null for aborted builds - maybe the best way is to make sure that getResult() will never return null as it is quite intuitive to assume that getResult() (at least for a past job) will never return null.

Still wonder why the reported line number in the stacktrace is incorrect.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138503#action_138503 ]

abayer commented on HUDSON-6429:
--------------------------------

Theoretically, getResult() should never return null, but yeah, I wouldn't be shocked if it still does in some weird cases.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138504#action_138504 ]

kutzi commented on HUDSON-6429:
-------------------------------

The constructor
protected Run(JobT job, long timestamp)

doesn't set the result initially, so maybe that's the cause?

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

drhudgins updated HUDSON-6429:
------------------------------


This was a sore spot for me as well until I put a try/catch(RuntimeException e) around the
if (mb.getPreviousBuiltBuild().getResult().isWorseThan(Result.SUCCESS))

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138506#action_138506 ]

abayer commented on HUDSON-6429:
--------------------------------

For the incremental build logic, if getResult() is null, what do you think the behavior should be? The easiest approach would be to add a check for mb.getPreviousBuiltBuild().getResult()==null ahead of the isWorseThan check in that if statement - so that if the previous build result for the module we're checking is null, we assume it needs to be built this time. This will result in some superfluous builds, but the only alternative I can think of is to check earlier builds, which would be ugly and error-prone.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

abayer reassigned HUDSON-6429:
------------------------------

    Assignee: abayer

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138508#action_138508 ]

kutzi commented on HUDSON-6429:
-------------------------------

I don't see what is so ugly about checking earlier builds ;-) but for me just assuming that the module needs to be build is IMO good enough in this case, as aborting builds should be the exception.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138510#action_138510 ]

kutzi commented on HUDSON-6429:
-------------------------------

Actually, I think that Run#getPreviousBuiltBuild should already skip builds with a null result.
At least it does fit to what that method is supposed to return IMHO.

And even better would be to make sure that Run#getResult will never ever return null (at least when the build is not running anymore). I've been bitten by a null result while developing a plugin already, too.

Of course, this is a much bigger change than just checking for null in MavenModuleSetBuild.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138751#action_138751 ]

kutzi commented on HUDSON-6429:
-------------------------------

Can we at least get the 'easy' solution - check if Result is null and assume module has to be build in that case - quickly?

Anything is better than the current NPE.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139275#action_139275 ]

kutzi commented on HUDSON-6429:
-------------------------------

Is there anything happening regarding this issue?
If not, I could try to create a patch for this on myself and attach it here for review.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139628#action_139628 ]

chomats commented on HUDSON-6429:
---------------------------------

I restarted a new job and it's ok.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6429) NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139627#action_139627 ]

chomats commented on HUDSON-6429:
---------------------------------

I had this problem : I renamed a module (change case only) and the next job failed.

> NullPointerException at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-6429
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6429
>             Project: Hudson
>          Issue Type: Bug
>          Components: maven2
>         Environment: Hudson 1.351, Maven 2.2.1
>            Reporter: kutzi
>            Assignee: abayer
>            Priority: Critical
>
> I've got this exception while running the build:
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> java.lang.NullPointerException
> at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:432)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> at hudson.model.Run.run(Run.java:1240)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:122)
> This seems to be similar to http://markmail.org/message/ni72qrruszvzp63m
> However, I'm on Hudson 1.351, so the bug should have been fixed in it, right?
> I've also a Maven job with incremental build option.
> The module with the changes had already been build before. The 3 builds before this failing build, however, were aborted manually.
> Deactivating the incremental build option and starting the build manually helped.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12