What about putting java -DTestSuite="My Regression Test" -cp test.jar org.testng.TestNG -d "testng-results" MyTest.xml into a batch file, create a build step that calls the batch file and archive the artifacts? I think that could help to get rid of that putative behaviour of Jenkins
On 4 Apr., 17:51, krikar <kristian.hermann.k...@gmail.com> wrote: > I think you're referring to > testng-plugin<https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin>, > but that does only publishing of testng test results, not actual launching > testng. > But thanks anyway, Kristian.
