There are no email-ext methods in the stack trace, so I am not sure that this is an email-ext issue at all. Is it reproducible?
Alex Earl
added a comment - There are no email-ext methods in the stack trace, so I am not sure that this is an email-ext issue at all. Is it reproducible?
Yes, it happens every time the configuration page is loaded.
Jenkins error page is inserted into the page flow. (Now hidden behind ERROR link)
The recipient list is $DEFAULT_RECIPIENTS.
The default recipients list is itself empty.
If the recipient list is empty, then there is no error.
This would be the expected behaviour.
Same for Reply-To.
James Howe
added a comment - - edited Yes, it happens every time the configuration page is loaded.
Jenkins error page is inserted into the page flow. (Now hidden behind ERROR link)
The recipient list is $DEFAULT_RECIPIENTS.
The default recipients list is itself empty.
If the recipient list is empty, then there is no error.
This would be the expected behaviour.
Same for Reply-To.
I tried with 1.611 and still couldn't replicate it. From the stack trace it doesn't even seem like its getting to the email-ext code, so I'm not sure where to go with the debug. If it comes up again with the latest Jenkins and plugin, please reopen.
Alex Earl
added a comment - I tried with 1.611 and still couldn't replicate it. From the stack trace it doesn't even seem like its getting to the email-ext code, so I'm not sure where to go with the debug. If it comes up again with the latest Jenkins and plugin, please reopen.
What is the value of the recipient list when this error occurs?