-
Bug
-
Resolution: Fixed
-
Major
-
None
Using the parameterized build trigger and email-ext
1) Create downstream job that emails the requestor using email-ext
2) Create upstream [Edit: multi-configuration only!] job that triggers downstream job using a condition to run the parameterized build trigger plugin
3) Run upstream job: receive null ptr exception when email-ext tries to email requestor.
- is related to
-
JENKINS-12300 Null pointer exception when downstream job is run from a Build Step where email Requester is selected
-
- Resolved
-
[JENKINS-12410] Downstream jobs not associated with upstream parent job properly
Component/s | New: email-ext [ 15538 ] | |
Component/s | New: parameterized-trigger [ 15592 ] | |
Component/s | Original: conditional-buildstep [ 15947 ] | |
Description |
Original:
Using the parameterized build trigger, email-ext, and conditional-buildstep: 1) Create downstream job that emails the requestor using email-ext 2) Create upstream job that triggers downstream job using a condition to run the parameterized build trigger plugin 3) Run upstream job: receive null ptr exception when email-ext tries to email requestor. This same bug used to occur without conditional-buildstep; when using the parameterized build trigger to run a downstream job the parent job would not be filled in properly. In the master branch of parameterized build trigger, this issue is fixed. (In the desciption page, the fix is: "Builds triggered as build steps will now appear as downstream builds. (issue #11082, issue #9263, issue #5184)") However, when you wrap a parameterized build trigger step in a conditional build step, the same issue still occurs where the downstream job does not have a record of which parent job triggered it. |
New:
Using the parameterized build trigger and email-ext 1) Create downstream job that emails the requestor using email-ext 2) Create upstream [Edit: multi-configuration only!] job that triggers downstream job using a condition to run the parameterized build trigger plugin 3) Run upstream job: receive null ptr exception when email-ext tries to email requestor. |
Component/s | Original: email-ext [ 15538 ] |
Assignee | Original: Dominik Bartholdi [ domi ] | New: huybrechts [ huybrechts ] |
I realized this issue is actually with parameterized build trigger. It only is visible when the upstream job is a multi-configuration project.