Oh boy X) This sounds a bit like a memory issue in Java. Did you try -XmX1024m or the like?
To answer your question, I think I have seen a plugin that notifies an upstream job...*scratch* Join plugin I think. But this requires to get creative. The join plugin interfaces between an up- and downstream job. It puts the upstream at hold until the downstream has finished. My idea at first thought (no warranty for a logic that makes sense): You would then to create 2 additional jobs. - 1 that is connected via join to the main job and runs the tests - 1 that is spawned by join as post-build action which skims the build log/text file/what ever of the testing downstreeam job for your key words to decide if the jobs is running successfully or not. That job will then run a single build task containing a condition. Let the task finish if everything is alright and break it if the key words indicate a failure. In DOS batch would "@echo epic failure dude && exit /B 1" break the task and let the entire job fail. I am content that *nix has a similar feature ^^ Hope that helps Jan On 5 Apr., 08:53, krikar <kristian.hermann.k...@gmail.com> wrote: > I will certainly try different approaches. > Yes, the tests runs for hours and hours :-) > > More interesting info. I can get the same behavior using VirtualBox. > If I launch the test on a VirtualBox guest from a host using following > command: > vboxmanage guestcontrol "$VM_NAME" exec --image "cmd.exe" --username > "user" --password "passwd" --wait-exit -- "/c java -cp test.jar > org.testng.TestNG -d testng-results MyTest.xml" > > The command will return after ~9 minutes, *but*, the test will go on > executing.The difference is that Jenkins stops the job. > > - Is there a way to start a Jenkins job, and let Jenkins wait for some > text to appear, and use that to decide if the job has passed or failed, no > matter what EOF or other occurred? > > /Kristian
