-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JENKINS-40979 add trigger cause messages #996
Changes from 7 commits
8469fe3
3487e0f
b6c82d6
ea5be6e
5ebe9be
9ee53a0
6586b86
07f3fe4
6d4c96e
02a0c1d
9cd8c9a
91d70ef
dcba389
8d0d0d3
08b4e59
c00a124
7800962
e7b2b4d
133061e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,7 +25,7 @@ public TreePruner accept(Object node, Property prop) { | |
|
||
// for merge properties, the current restrictions on the property names should | ||
// still apply to the child TreePruner | ||
if (prop.merge) | ||
if (prop.merge && child != null) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @vivek Use of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, please open a PR in stapler with this fix. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed jenkinsci/stapler#112 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍 |
||
child = new FilteringTreePruner(predicate,child); | ||
|
||
return child; | ||
|
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.
@vivek I have skipped serialisation of
Item
andRun
objects in case they are returned by aCause
object. These are evil for performance reasons anyway. I have checked implementations in core and I can't see any that do this but I've added it to be on the safe side (who knows what plugins will do).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.
Its a hack but should be fine until we find something else pulling in something else during serialization thats not item or run. We can revisit if its trouble later on.