• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins 2.204.1, build-failure-analyzer-plugin 1.24.2

      Expected behavior:

      the plugin detects two failure causes. Both failure causes are displayed in the list view.

      Actual behavior:

      the plugin detects two failure causes. Only the first failure cause is displayed in the list view.

       

          [JENKINS-60708] Only one cause is shown in list view

          Ian Williams added a comment -

          Not an expert, just a user of the plugin, but my expectation is once you fail, you fail.; you can't fail again. Most jobs stop/exit upon first failure. Perhaps what you are seeking to do is distinguish between failure that reports a failure (eg: java.io.IOException) and different subsequent causes. In that case, you probably want multiline regex that match the different contexts. That was our scenario. Or just match the specific second failure/cause(s).

          Ian Williams added a comment - Not an expert, just a user of the plugin, but my expectation is once you fail, you fail.; you can't fail again. Most jobs stop/exit upon first failure. Perhaps what you are seeking to do is distinguish between failure that reports a failure (eg: java.io.IOException) and different subsequent causes. In that case, you probably want multiline regex that match the different contexts. That was our scenario. Or just match the specific second failure/cause(s).

          Hi ianw, thank you for your participation.

          After a build fails, the plugin uses the configured set of regular expressions to scan the log for failure causes. Multiple causes are possible. All failure causes are detected as expected, but not displayed in the list view. The build monitor, for example, displays two failure causes, the list view just one.

          Florian Butter added a comment - Hi ianw , thank you for your participation. After a build fails, the plugin uses the configured set of regular expressions to scan the log for failure causes. Multiple causes are possible. All failure causes are detected as expected, but not displayed in the list view. The build monitor, for example, displays two failure causes, the list view just one.

          In case "someone" is using plugin with jenkins jobs executing automated tests to gather statistics on test failure causes it would be extremely beneficial to be able to list all failure causes (defined in the Failure Cause Management section).

          Pekka Mäki-Asiala added a comment - In case "someone" is using plugin with jenkins jobs executing automated tests to gather statistics on test failure causes it would be extremely beneficial to be able to list all failure causes (defined in the Failure Cause Management section).

          I have a similar use case as Pekka.  If multiple test cases fail, but I only have 1 rule that is searching for "test case failed.+)"   I only see one failure cause listed in the emails etc.  I want all the failed test cases to show in the email, so people can just look at the email and not have to go to the build. 

          David Beleznay added a comment - I have a similar use case as Pekka.  If multiple test cases fail, but I only have 1 rule that is searching for "test case failed .+)"   I only see one failure cause listed in the emails etc.  I want all the failed test cases to show in the email, so people can just look at the email and not have to go to the build. 

            t_westling Tomas Westling
            fbutter Florian Butter
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: