The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.
For a list of other such plugins, see the Pipeline Steps Reference page.
findText: Search files or the console log for regular expression(s)alsoCheckConsoleOutput (optional)
booleanbuildResult (optional)
StringfileSet (optional)
StringnotBuiltIfFound (optional)
booleanregexp (optional)
StringsucceedIfFound (optional)
booleantextFinders (optional)
regexpregexp
Pattern class.
StringalsoCheckConsoleOutputalsoCheckConsoleOutput (optional)
booleanbuildResultbuildResult (optional)
SUCCESS if the current result is UNSTABLE or worse. Use SUCCESS to keep the build result from being set.
StringchangeConditionchangeCondition (optional)
MATCH_FOUND, then the build result will be set if a match is found. If the change condition is MATCH_NOT_FOUND, then the build result will be set if a match is not found.
MATCH_FOUND, MATCH_NOT_FOUNDfileSetfileSet (optional)
logs/**/*/*.txt. See the documentation for the @includes attribute of the Ant FileSet type for details. Leave this empty if you do not want to scan any files (usually combined with checking Also search the console output).
StringunstableIfFound (optional)
booleanPlease submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.