Well, my email template is writtern in HTML format.

When I reads the content of the HTML email body, I found that the page contained
no failure cause, so it cannot be the email client's fault. And I've no
idea what's going on. :-(

Is there any debug options which could show me the whole procedure of
the parsing?

BTW, is there a better way to refer to another plugin in my email template? 
It could be my fault, maybe. :-)
-- 
Levski Weng

www.levskiweng.me
On Wed, Mar 19, 2014 at 12:34:44PM -0700, Slide wrote:
 | This is VERY odd since all of the processing is done on the server side. Is
 | it possible that the markup is there, but just not showing up in the other
 | browsers? Can you look at the source in the browsers that do not work and
 | see if its in there? Are you doing a plain text email, or html?
 | 
 | 
 | On Mon, Mar 17, 2014 at 7:21 PM, Levski Weng <[email protected]> wrote:
 | 
 | > I'm writing a email template in groovy, but when I test the email template
 | > in
 | > different browsers(Firefox 27/Opera Next), the testing result is different.
 | > What I want is to grab the failure cause in another Jenkins plugin called
 | > Build Failure Analyzer.
 | >
 | > The relative email template is attached below:
 | > -------------
 | >
 | > <%      def foundErrorReason = false
 | >         if (build.result.toString() != 'SUCCESS') { %>
 | >
 | > FAILURE CAUSE ANALYSIS
 | > <%              build.badgeActions.each() {faa -> %>
 | > <%                      if (faa.displayName == 'Failure Cause Management')
 | > {
 | >                                 faa.getFoundFailureCauses().each() { ffc
 | > -> %>
 | > <%                                      foundErrorReason = true %>
 | > ${ffc.getName()}
 | >
 | > ${ffc.getDescription()}<BR/>
 | > <%                              } %>
 | > <%                      } %>
 | > <%              } %>
 | > <%              if (!foundErrorReason) { %>
 | > Cannot identify causes of the failure, please refer to the console log.
 | > <%              } %>
 | >
 | > <%      } %>
 | > ------------
 | > When I test the template in Firefox 27, everything works fine to me and it
 | > shows the failure cause defined by myself, but the Opera Next tells me it
 | > cannot find any failure cause.
 | >
 | > Also I've tested the email template by putting it into a job and I build
 | > the
 | > job in order to trigger the email sending, but when I receive the email,
 | > the
 | > email still tells me that it can't find the failure cause.
 | >
 | > Could anyone here tell me why?
 | > Any suggestion will be appreciated.
 | >
 | >
 | >
 | > --
 | > View this message in context:
 | > 
http://jenkins-ci.361315.n4.nabble.com/The-result-of-the-email-template-testing-is-different-in-different-web-browsers-tp4694979.html
 | > Sent from the Jenkins users mailing list archive at Nabble.com.
 | >
 | > --
 | > You received this message because you are subscribed to the Google Groups
 | > "Jenkins Users" group.
 | > To unsubscribe from this group and stop receiving emails from it, send an
 | > email to [email protected].
 | > For more options, visit https://groups.google.com/d/optout.
 | >
 | 
 | 
 | 
 | -- 
 | Website: http://earl-of-code.com
 | 
 | -- 
 | You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
 | To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
 | For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to