This plugin lets you search keywords in the files you specified and use that to downgrade a "successful" build to be unstable or a failure.This is handy when you have some tools in your build chain that don't use the exit code properly.

The search is always performed, even on builds which returned a non-zero exit status, but the reclassification only applies to builds which returned an overall exit status of zero.

Unknown User (bazthemail@gmail.com)

Would you please provide an example on how to search multiple strings from the console log? For example, search for three keywords: "^Error:", "FATAL ERROR", and "ERRORE:". I tried and without succeed.

Unknown User (gunner_1980)

Does this have the ability to search for multiple regular expressions and return different results based off of them? From the looks of it you can only pass/fail or choose unstable based off of the searched. For example I would like to be able to fail the build if it finds one regular expression or show a build as unstable if it finds another. Right now it looks like it is all or nothing but it would be really nice to be able to specify a regex that would trigger a build fail and another regex that would trigger a build unstable. The fail would of course need to override any unstable regex's that are found.

The documentation for this plugin could be improved a lot - in particular, it would be very helpful if it said

"This plugin can be used to downgrade a successful build to "unstable" or "failure" if a regular expression matches in a set of files.
For example, it can be used to search for the string "failure" in a set of log files."

The current description on this page seems to cover the points you make.

As designed, though, the capabilities seem to be limited though:

The ability to set either unstable or failed, depending upon what strings are found (Geoff's suggestion)

The ability to promote a failed build (in the case of extenuating circumstances for things that crash predictably)

The ability to downgrade a build to aborted

I would like to mark builds aborted in certain circumstances -- for instance when the necessary pre-conditions to perform a successful build have not been met. When we run our script, the only outcomes (without manual intervention) are failed, succeeded, or unstable, but we already have meaningful scenarios for these. We could just keep waiting, but then that means it would be a while for people to understand what is going on.