• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • log-parser-plugin
    • None

      We have a large number of projects in Hudson, with dependencies between each other. If the log parser finds warnings in the log, I want the build to be unstable. As it is now, the log parser can only fail the build, which will prevent the downstream builds from running.

      It is now possible to fail the build on error. Please make it possible to also make the build instable on warning.

          [JENKINS-7853] Allow Log Parser Plugin to make build unstable

          hbjastad added a comment -

          I just had a look at the source code, and adding this feature is so easy I don't even see the value in creating a patch for it. You just copy/paste the code for failBuildOnError and rename it to instableOnWarning

          hbjastad added a comment - I just had a look at the source code, and adding this feature is so easy I don't even see the value in creating a patch for it. You just copy/paste the code for failBuildOnError and rename it to instableOnWarning

          hbjastad added a comment -

          Attached:
          1. Diff file for src/main/java/hudson/plugins/logparser/LogParserPublisher.java and src/main/resources/hudson/plugins/logparser/LogParserPublisher/config.jelly
          2. New file src/main/webapp/unstable_on_warning.html

          hbjastad added a comment - Attached: 1. Diff file for src/main/java/hudson/plugins/logparser/LogParserPublisher.java and src/main/resources/hudson/plugins/logparser/LogParserPublisher/config.jelly 2. New file src/main/webapp/unstable_on_warning.html

          jborghi added a comment -

          Incorporated patch from hbjastad. Thanks for the fix!

          jborghi added a comment - Incorporated patch from hbjastad. Thanks for the fix!

            jborghi jborghi
            hbjastad hbjastad
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: