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

Add possibillity to copy / "alias" warning parser

    XMLWordPrintable

Details

    Description

      The warning plugin is a nice and powerful tool.
      There are several build-in parsers existing for standard formats.
      The statistics and graphs are separated depending on the chosen parser.

      In my / our case we have several tools / builds within the same job which give warnings that can be parsed by the same (eg. gcc4) parser. It would be very nice if it would be possible to have an own chart / statistics etc. for each of the tools / buildtypes, since in this case it is easier / faster to reproduce and work on the certain warning, filter relevant ones for a given use case etc. .

      So the idea is to have the easy available possibility of a renamed / aliased parser using the regex / algorithm of the parent parser, but stores / publishes the results in an own list / chart / etc.
      The configuration might be similar to the own groovy script ones, just choose the parent parser form the existing and add the alias names...
      Afterwards, if the output of the tools is found in separated files it would be possible to parse each with its own "parser" .

      This could be also very helpful in pipeline jobs to differ the results of several stages...
      thx

      Attachments

        Issue Links

          Activity

            hmm I cannot see how to do this without the need of

            • recreate the regex by myself (where I might oversee something)
            • find out how to call that other parser in the groovy script (didn't find snippet by googling so far).

            if this is still possible without to much extra effort it might be a good idea to shortly document that in the plugins wikipage or in the dynamic parser help itself.

            thx

            dergruebel Lukas Goormann added a comment - hmm I cannot see how to do this without the need of recreate the regex by myself (where I might oversee something) find out how to call that other parser in the groovy script (didn't find snippet by googling so far). if this is still possible without to much extra effort it might be a good idea to shortly document that in the plugins wikipage or in the dynamic parser help itself. thx
            drulli Ulli Hafner added a comment -

            The other issue still is open, it makes no sense to have two issues open with basically the same content... Or is your use case a different one that is not solved if JENKINS-18708 is solved?

            drulli Ulli Hafner added a comment - The other issue still is open, it makes no sense to have two issues open with basically the same content... Or is your use case a different one that is not solved if JENKINS-18708 is solved?
            drulli Ulli Hafner added a comment -

            Please leave your comments in JENKINS-18708.

            drulli Ulli Hafner added a comment - Please leave your comments in JENKINS-18708 .

            duplicate to be fixed...

            dergruebel Lukas Goormann added a comment - duplicate to be fixed...

            People

              drulli Ulli Hafner
              dergruebel Lukas Goormann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: