Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Release notes for 1.11
Wiki Markup
{jenkins-plugin-info:text-finder}
Excerpt

This plugin lets you search for keywords in the files you specified

...

(or the console log) and possibly downgrade a "successful" build to

...

a status of unstable, failure, or not built.

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.

Change Log

...

Usage

The basic pipeline syntax is as follows:

    findText regexp: '<regular expression>', fileSet: '<file set>'

The regular expression uses the syntax supported by the Java Pattern class. The file set specifies the path to the files in which to search, relative to the workspace root. This can use wildcards, like logs/**/*/*.txt. See the Ant FileSet documentation for details.

To also check the console log, use the following syntax:

    findText regexp: '<regular expression>', fileSet: '<file set>', alsoCheckConsoleOutput: true

Note that if you just want to check the console log, you can omit the file set:

    findText regexp: '<regular expression>', alsoCheckConsoleOutput: true

To customize the build result, you can use any combination of succeedIfFound, unstableIfFound, or notBuiltIfFound. For example, to mark the build as unstable if the expression is found:

    findText regexp: '<regular expression>, alsoCheckConsoleOutput: true, unstableIfFound: true

Changelog

Version 1.11 (June 1, 2019)
  • Add pipeline support (#12)
  • Add option to set build as not built (#16)

  • Better log output to console (#21)
Version 1.10 (Jan 31, 2014)
  • No longer blocking concurrent builds. (JENKINS-17507)
  • Cleaner config UI using help buttons
  • Japanese translation

...