If you look at the message from Jenkins, it seems Jenkins is not happy with the last-modified attribute of the xml file. If Jenkins sees the xml file is older than the build, it thinks the file might be a left-over from an earlier build. This is a common mistake if people assume build always start with an empty workspace. It doesn't, unless you specifically configure it to be so.
Another possibility is the xml file has actually been checked into the version control by someone. Yet another possibility is clocks aren't synchronized in your Jenkins server, your file server and your version control server. Unsynchronized clocks are an easy way to generate strange errors that are loads of fun to debug! -- Sami Nig kirjoitti 16.7.2012 kello 12.27: > Hi, > > I've installed testng-6.5.2 and version 0.32 of the pulgin but no results > are displayed. > > The following is logged in the Console Output: > TestNG Reports Processing: START > Looking for TestNG results report in workspace using pattern: > **/testng-results.xml > testng-results.xml was last modified before this build started. Ignoring it. > Saving reports... > Found matching files but did not find any TestNG results. > > The testng-results.xml file is attached. > > Am I doing something wrong ? > > Thanks ! > > <testng-results.xml>
