Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22935

Only one line is highlighted per identifier.

XMLWordPrintable

      For each identifier that BFA has access to, only one line is highlighted in the logs.

      Any number of lines per identifier should be able to be highlighted (multiple errors of the same type).

          [JENKINS-22935] Only one line is highlighted per identifier.

          Aaron Haaf created issue -

          J John added a comment -

          When can this bug be addressed?

          J John added a comment - When can this bug be addressed?

          Tomas Westling added a comment -

          This is a design choice we took when we created the first version of the plugin, so I wouldn't call it a bug.
          We assumed that the first instance of an error is the most interesting and chose to highlight that one.
          We don't feel this is a pressing issue, rather a feature request, so if you have a good solution, we gladly accept
          contributions.

          Tomas Westling added a comment - This is a design choice we took when we created the first version of the plugin, so I wouldn't call it a bug. We assumed that the first instance of an error is the most interesting and chose to highlight that one. We don't feel this is a pressing issue, rather a feature request, so if you have a good solution, we gladly accept contributions.

          J John added a comment -

          That makes sense. It will be useful if there is a flag to enable repeated highlight for an indication.

          I need this to identify multiple test failures (out of 600 tests) against a build.

          J John added a comment - That makes sense. It will be useful if there is a flag to enable repeated highlight for an indication. I need this to identify multiple test failures (out of 600 tests) against a build.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 155081 ] New: JNJira + In-Review [ 179007 ]

          Sorin Sbarnea added a comment -

          t_westling: that is a genuine bug which cripples user experience but I do also understand your reasons for doing it. I am fully aware that a single bad pattern could take jenkins down due to too many matches.

          I think that the best way to implement it is to add a variable (system properly?) that limits the number of matches, and that defaults to 1 (current behaviour).

          Once implemented I would gladly change the value to 10 which seem like a good compromise.

          PS. Remember that these matches could be scattered in very distant places in the console log, so identifying them does help a lot.

          Sorin Sbarnea added a comment - t_westling : that is a genuine bug which cripples user experience but I do also understand your reasons for doing it. I am fully aware that a single bad pattern could take jenkins down due to too many matches. I think that the best way to implement it is to add a variable (system properly?) that limits the number of matches, and that defaults to 1 (current behaviour). Once implemented I would gladly change the value to 10 which seem like a good compromise. PS. Remember that these matches could be scattered in very distant places in the console log, so identifying them does help a lot.

            t_westling Tomas Westling
            ahaaf Aaron Haaf
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: