The plugin detects the first occurrence only of the same failure cause if it contains a regex pattern ... For example, I have this pattern ".* is not recognized as an internal or external command," and it highlights only the first occurrence, although it should match both errors:

        

          [JENKINS-58214] patterns with regex are detected once only

          I am experiencing the same issue.

          BFA does not indicate all occurences of a certain failure cause but only the first occurence.
          However, finding/showing all occurences would be more than just helpful.

          Can you please solve this?
          (Or add it as a feature if the current behaviour is intended.)

          Christoph Obermair added a comment - I am experiencing the same issue. BFA does not indicate all occurences of a certain failure cause but only the first occurence. However, finding/showing all occurences would be more than just helpful. Can you please solve this? (Or add it as a feature if the current behaviour is intended.)

          North added a comment -

          I have reported it as a feature, not a bug, here https://issues.jenkins.io/browse/JENKINS-72793

          North added a comment - I have reported it as a feature, not a bug, here https://issues.jenkins.io/browse/JENKINS-72793

          Dennis added a comment - - edited

          Hello,  HealthInsuranceMarket

          It seems like the issue you’re encountering is related to the regex pattern matching only the first occurrence of the specified string. This behavior is typically due to the absence of the global flag (g) in your regex pattern. The global flag ensures that the pattern matches all occurrences of the string, not just the first one.

          Here’s a modified version of your regex pattern that includes the global flag:

          /.* is not recognized as an internal or external command,/g

          By adding /g at the end of the pattern, it should now match every occurrence of the error message in your text.

          If you’re using a specific tool or programming language, the syntax for including the global flag might differ. For instance, in JavaScript, you would use the pattern as shown above, but in other languages or tools, the way to specify a global search might be different.

          Dennis added a comment - - edited Hello,   HealthInsuranceMarket It seems like the issue you’re encountering is related to the regex pattern matching only the first occurrence of the specified string. This behavior is typically due to the absence of the global flag (g) in your regex pattern. The global flag ensures that the pattern matches all occurrences of the string, not just the first one. Here’s a modified version of your regex pattern that includes the global flag: /.* is not recognized as an internal or external command,/g By adding /g at the end of the pattern, it should now match every occurrence of the error message in your text. If you’re using a specific tool or programming language, the syntax for including the global flag might differ. For instance, in JavaScript, you would use the pattern as shown above, but in other languages or tools, the way to specify a global search might be different.

            t_westling Tomas Westling
            hamed Ahmed Hamed
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: