|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Taiki Sugawara: I'm using the text-finder and the naginator plugin. At the text-finder plugin, I search at the console output for the _expression_ "Timed-out after waiting 720 seconds for emulator" (leave "Files" empty). If this _expression_ was found then the build will be unstable (check the unstable if found checkbox).
At the naginator plugin I checked the "Rerun build for unstable builds as well as failures" checkbox and I try again to run the job after 500 seconds (shorter is possible too). I configuered also that the build will be repeated 5 times.
I hope this will help you with your problem.
EDIT: At the naginator plugin you need to open the extended options and check "only rerun build if regular _expression_ is found in output" and paste the time-out message into the "regular _expression_ to search for" field. Without this the build will be repeated even the build is failing because of a source code error.
@Richard Mortimer: Maybe you can add this workaround to your documentation.