Though it's easy to add a workaround code not to cause NPE, I want to know what happens internally. But I can't reproduce the problem as I don't use CloudBees Jenkins Platform.
Would anyone see that and let me know followings?
* Why `null` is passed to `@AncestorInPath`? * Is there better way to fix? * I believe it can be fixed by changing the class of `@AncestorInPath`.
Regards, ikedam
Ikedam
unread,
Feb 28, 2016, 6:24:23 PM2/28/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Developers
> * Why `null` is passed to `@AncestorInPath`? > * Is there better way to fix? > * I believe it can be fixed by changing the class of `@AncestorInPath`.
Resolved. The reporter updated the JIRA comment so that I know aboves now.