email-ext 2.34 not including sample templates

2013-09-19 Thread jaziniho 
Hi,

I've just downloaded and installed email-ext 2.34 on a recently setup 
jenkins instance.
The documentation refers to sample jelly scripts which can be found:
plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/

However, I've checked my installation and there are no such template files 
there.
In fact, the only contents of plugings/email-ext/WEB-INF/ is a directory 
called lib/ with jar files and a licenses.xml

Are these sample templates still supposed to ship with the email-ext plugin?
Is it likely that I've had some issue during plugin installation, or maybe 
it's possible the plugin was mis-packaged in latest release?
2.34 was only issued on 15th Sep.


Cheers,
Tom

-- 
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.

incremental push of JUnit test results to Jenkins

2013-08-06 Thread jaziniho 
Hi,

I'm looking to find if there is any existing method for incrementally 
pushing Junit results to Jenkins.

For example:
A test suite is started, which is described by a JUnit Test Report.
As each test case is run, it posts the results of the test back to Jenkins. 
(Perhaps via REST or some other API).

>From what I understand, this more usual process is that a TestReport is 
generated after all test cases in the test suite have run, and is then 
published as a single XML file for Jenkins to consume.

Description of the situation:
Currently, triggering a test suite is simply sending the test set to our 
internal job management system, which handles the scheduling of them 
against a large compute cluster.
If the test suite is successfully scheduled to be run, then the step is 
marked as having succeeded.

We have it setup this way because the test suites are very intensive -- 
depending on the run it can take over a week to complete.
Rather than waiting until the end of the test suite to publish results, we 
would like each test case to push its result up to Jenkins.

This incremental progress reporting would allow better monitoring of jobs 
throughout the week.

Are there any existing plugins or tools associated which allow such a work 
flow?

Cheers,
Tom

-- 
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.