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

Provide a way to clean up console log before handing it to parser

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Component/s: warnings-ng-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.127, Warnings Plugin 4.66
    • Similar Issues:

      Description

      For every new build, all compiler warnings are considered "fixed", and then re-reported as "new".

      Initially I had guessed that it was because different build machines were checking the project out in different locations, but it turns out the absolute paths are identical too.

        Attachments

          Activity

          Hide
          trejkaz trejkaz added a comment -

          We tried using Timestamper Plugin already, and there are multiple bugs preventing its use with pipeline, but mainly it causes the logs to be 3+ times larger due to all the excess serialised data, which makes the entire build take longer to run, logs take longer to view, and so forth.

          Maybe "console timestamp" refers to a different plugin though?

          Show
          trejkaz trejkaz added a comment - We tried using Timestamper Plugin already, and there are multiple bugs preventing its use with pipeline, but mainly it causes the logs to be 3+ times larger due to all the excess serialised data, which makes the entire build take longer to run, logs take longer to view, and so forth. Maybe "console timestamp" refers to a different plugin though?
          Hide
          trejkaz trejkaz added a comment -

          Is there some way we can format the timestamp prefixes which will get it to be ignored by the parser? I figure when you run an Ant build, a lot of output is prefixed there too, so there must be a way to avoid it.

          Show
          trejkaz trejkaz added a comment - Is there some way we can format the timestamp prefixes which will get it to be ignored by the parser? I figure when you run an Ant build, a lot of output is prefixed there too, so there must be a way to avoid it.
          Hide
          drulli Ulli Hafner added a comment -

          I think a simple workaround would be to pipe the output to a file and remove the prefixes using a shell command. In the upcoming 5.x release it is possible to provide a preprocessor for the text that is scanned. However, it is not configurable in the UI in the moment.

          Show
          drulli Ulli Hafner added a comment - I think a simple workaround would be to pipe the output to a file and remove the prefixes using a shell command. In the upcoming 5.x release it is possible to provide a preprocessor for the text that is scanned. However, it is not configurable in the UI in the moment.
          Hide
          drulli Ulli Hafner added a comment -

          I think it would rather make sense to pipe the compiler output to a file before the console log is prefixed with custom timestamps.

          Show
          drulli Ulli Hafner added a comment - I think it would rather make sense to pipe the compiler output to a file before the console log is prefixed with custom timestamps.
          Hide
          drulli Ulli Hafner added a comment -

          I think that the plugin can't do anything here. If you change the log output manually it would make sense to pipe the log to a separate file before you annotate the log. Or use the same invisible markers to identify the time stamps.

          Show
          drulli Ulli Hafner added a comment - I think that the plugin can't do anything here. If you change the log output manually it would make sense to pipe the log to a separate file before you annotate the log. Or use the same invisible markers to identify the time stamps.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            trejkaz trejkaz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: