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

Change Log Parser to act as filter on ConsoleStream so that reported results are available during job execution

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • log-parser-plugin
    • None

      The LogParser could be installed as a filter on the console output stream, running as the stream is written, so that the error/warning/info counts would be available as the job proceeds, and so that the cost of pattern matching is spread over the whole job. For long running jobs this provides valuable information about the progress of the job.

          [JENKINS-9149] Change Log Parser to act as filter on ConsoleStream so that reported results are available during job execution

          Matthew Kruer added a comment -

          If done correctly doing it this would allow parsed logs to be generated on the fly from the log file itself. This allows the rules to be applied to existing build logs as well.

          Matthew Kruer added a comment - If done correctly doing it this would allow parsed logs to be generated on the fly from the log file itself. This allows the rules to be applied to existing build logs as well.

          Andrew Barnish added a comment -

          I guess this might solve the issue where the current log parser crashes the entire Jenkins instance with very large log files (>100MB)
          This seems to be because it loads the entire log into memory which causes java.lang.OutOfMemoryError: Java heap space

          Andrew Barnish added a comment - I guess this might solve the issue where the current log parser crashes the entire Jenkins instance with very large log files (>100MB) This seems to be because it loads the entire log into memory which causes java.lang.OutOfMemoryError: Java heap space

            rgoren rgoren
            marvingreenberg marvin greenberg
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: