Got it, thanks!
On Friday, March 15, 2013 1:38:23 PM UTC-7, slide wrote:
>
> My guess is that you are accessing something in your script/template that
> is null. The exceptions you are getting are all going to be based on what
> you are doing in your template/script, so you're just going to have
I should have make it clear that I didn't modify anything related to the
template or content generation. My changes were around triggers and
timing of the email sending.
On Friday, March 15, 2013 12:20:23 PM UTC-7, Kevin Fleming wrote:
>
> If you are making changes to the plugin, you need to
My guess is that you are accessing something in your script/template that
is null. The exceptions you are getting are all going to be based on what
you are doing in your template/script, so you're just going to have to
debug it more. You can look at the wiki for ways of debugging the
templates/scri
If you are making changes to the plugin, you need to take the time to analyze
the problems that occur and figure out whether your changes might be at fault.
The rest of the people on this list don't have access to your modified source
code and at best they could only guess at what might be going
Just had another exception
[[ Exception while replacing SCRIPT. Please report this as a bug. ]] {{
java.lang.NullPointerException }}
Any ideas?
On Friday, March 15, 2013 8:48:47 AM UTC-7, slide wrote:
>
> I'll try and improve the error message, it should not tell you to report
> it as a bug.
I'll try and improve the error message, it should not tell you to report it
as a bug. I filed [1] in order to track the issue.
Thanks,
slide
1 - https://issues.jenkins-ci.org/browse/JENKINS-17234
On Fri, Mar 15, 2013 at 8:22 AM, cchen wrote:
> I see. thank you for the quick response!
>
>
>
I see. thank you for the quick response!
On Friday, March 15, 2013 7:29:28 AM UTC-7, slide wrote:
>
> It looks like you are doing something in your template that is causing the
> exception. You are trying to use a variable called "failing" which doesn't
> exist.
>
>
> On Thu, Mar 14, 2013 at 11
It looks like you are doing something in your template that is causing the
exception. You are trying to use a variable called "failing" which doesn't
exist.
On Thu, Mar 14, 2013 at 11:59 PM, cchen wrote:
> Hello,
>
> I pulled master of emial-ext on 3/6 and made some modifications. 50% of
> the
Hello,
I pulled master of emial-ext on 3/6 and made some modifications. 50% of
the times, I see the following exception from one groovy email template
which is that different from our other templates. Any ideas? thanks!
[[ Exception while replacing SCRIPT. Please report this as a bug. ]] {{
