Here you go. https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin#Email-extplugin-TestingTemplates
slide On Fri, Apr 19, 2013 at 10:47 AM, Chris Withers <ch...@simplistix.co.uk>wrote: > Where's the right place on the wiki to look for this? > > Chris > > > On 26/02/2013 18:07, Slide wrote: > >> As I said, the groovy script console can be used to do quite a bit of >> stuff, I'll try and do a write-up tonight and post to the wiki. >> >> >> On Tue, Feb 26, 2013 at 11:01 AM, Josh Unger <joshung...@gmail.com >> <mailto:joshung...@gmail.com>> wrote: >> >> Thanks, I'll take a look at the Groovy. Any recommended approaches >> for quickly testing the Groovy? >> >> >> On Tue, Feb 26, 2013 at 5:06 AM, Slide <slide.o....@gmail.com >> <mailto:slide.o....@gmail.com>**> wrote: >> >> Honestly, I have been recommended people move off of the Jelly >> templates and use the groovy scripts/templates (see the SCRIPT >> token). It has more power, its easier to use and you can >> prototype stuff in the script console to some degree. >> >> 1) This would just be a matter of getting the CaseResult objects >> from the test failures list and using the correct getters for >> the info you want. >> >> 2) You'd have to iterate through the builds for the project, >> starting at the current build number and going backward to find >> the previous failure, then you could get its info just like you >> can the current build. >> >> These sorts of things are painful at best with Jelly, groovy >> provides a much easier way. >> >> >> On Mon, Feb 25, 2013 at 6:05 PM, Josh Unger >> <joshung...@gmail.com <mailto:joshung...@gmail.com>> wrote: >> >> Bummer. Ok, I'd like to modify the default HTML Jelly >> template to include two things. Maybe you could provide >> some pointers or a sample that already does this? >> >> 1. The default includes the test method failures. I'd like >> the actual output of all failed tests included inline. That >> is the Error Message and the Stacktrace. >> >> 2. When the build fails or goes unstable, I'd like to >> display a message in the title or body that says "x days >> since last screw up". : ) I see the Last Failure column >> but on my version (1.477) it displays a lot of N/As for some >> reason. This would just be a date diff of >> ${it.timestampString} and Last Failure I guess. >> >> Thanks. >> >> -josh >> >> >> On Mon, Feb 25, 2013 at 5:45 PM, Alex Earl >> <slide.o....@gmail.com <mailto:slide.o....@gmail.com>**> >> wrote: >> >> Sadly there currently isn't a nice way to do this. There >> is a bug filed requesting the ability to test using a >> previous build, but I haven't had a chance to implement >> it. >> >> Sent from my Windows Phone >> ------------------------------** >> ------------------------------**------------ >> >> From: Josh Unger >> Sent: 2/25/2013 17:36 >> To: >> jenkinsci-users@googlegroups.**com<jenkinsci-users@googlegroups.com> >> >> <mailto:jenkinsci-users@**googlegroups.com<jenkinsci-users@googlegroups.com> >> > >> >> Subject: Quickly testing Jelly templates with email-ext? >> >> The Email-ext of Jenkins allows you to write a Jelly >> email template. How do you write and test one without >> triggering a build every time? Basically, I'm looking >> for a 1 second iteration where I can modify a Jelly >> script, hit refresh on a browser, and it will >> automatically render the template (that would be sent >> out by email-ext) based upon a hard-code project and >> build result. >> >> I also posted the question to StackOverflow if you >> prefer answering this way - >> >> http://stackoverflow.com/**questions/15071475/quickly-** >> testing-jelly-templates-in-**email-ext-of-jenkins<http://stackoverflow.com/questions/15071475/quickly-testing-jelly-templates-in-email-ext-of-jenkins> >> >> Thanks. >> >> -josh >> >> -- >> 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 >> >> jenkinsci-users+unsubscribe@**googlegroups.com<jenkinsci-users%2bunsubscr...@googlegroups.com> >> >> <mailto:jenkinsci-users%**2bunsubscr...@googlegroups.com<jenkinsci-users%252bunsubscr...@googlegroups.com> >> **>. >> >> For more options, visit >> >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> >> >> >> >> -- >> Website: http://earl-of-code.com >> >> >> >> >> >> -- >> 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 >> jenkinsci-users+unsubscribe@**googlegroups.com<jenkinsci-users%2bunsubscr...@googlegroups.com> >> . >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> >> ______________________________**______________________________** >> __________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________**______________________________** >> __________ >> > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
