Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FIXED JENKINS-9822] occasional NPE when running maven jobs
- Loading branch information
Showing
2 changed files
with
9 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
345b3bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello Kutzi,
isn't this just disguising the actual bug? We should at least log a warning that something weird is happening in line #591.
Regards
Mirko
345b3bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
I don't know for sure if it's a bug then. The parent MavenModuleSetBuild might have been gone for any reason - might be there are non-bug related reasons, too ;-)
Anyway, there's no need to break this MavenBuild, if it can still finish without the existence of its parent build
345b3bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
345b3bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with mfriedenhagen that this just hides the bug. If the business of remembering modules to build again next time isn't strictly necessary, then the fix seems fine, but logging might be a good idea...