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

Make it possible to have several files as input for one parser

    XMLWordPrintable

Details

    • 5.0.0-beta2

    Description

      I have a project with 3 different doxygen documentations. Each of them has it's own warnings-file. For example Projects\Doxygen\warning.txt, Projects\Doxygen\ModuleTestsWarning.txt, Projects\Doxygen\IntegrationTestsWarning.txt.
      The Project page has several "Doxygen Warnings" links on the left side but they all link to the same page and the all link to the same page "jenkins/job/Hit1k-1_V01/warnings10" where it says that there are 15 new Warnings, but it is not posible to see in which file. If I click the link with these 15 new warnings i come to page "warnings10Result/new/?" where it says, that there are 0 new warnings. So it seem as if the plugin mixes the information of the three warning-files.

      Attachments

        Issue Links

          Activity

            drulli Ulli Hafner added a comment -

            Released in 5.0.0-beta2.

            drulli Ulli Hafner added a comment - Released in 5.0.0-beta2.
            drulli Ulli Hafner added a comment -

            I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page. Can you please read it carefully and comment or change it accordingly?

            drulli Ulli Hafner added a comment - I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page . Can you please read it carefully and comment or change it accordingly?

            drulli:
            sounds great...
            additionally that would give the possibility to "rename" the parsers output for less confusion in the dev-team in case a parser is just reused (once) for different than original tool...

            thumps up for that solution.

            dergruebel Lukas Goormann added a comment - drulli : sounds great... additionally that would give the possibility to "rename" the parsers output for less confusion in the dev-team in case a parser is just reused (once) for different than original tool... thumps up for that solution.
            drulli Ulli Hafner added a comment -

            Here is a possible solution:

            In the Job configuration it should be possible to specify the same parser multiple times. For each reference a pattern can be specified. Additionally all describing properties must be provided (see dynamic parser): Link name of project action, Graph name, etc.

            drulli Ulli Hafner added a comment - Here is a possible solution: In the Job configuration it should be possible to specify the same parser multiple times. For each reference a pattern can be specified. Additionally all describing properties must be provided (see dynamic parser): Link name of project action, Graph name, etc.
            hu3b10q7 Csaba Gyorfi added a comment -

            I have the same issue. In my build project there are two GNU/C++ project and I want to see the results separated, in two graphs. But this is not working as described.
            As a workaround, it would be nice if I could clone the GNU/C++ parser with a new name, and than use this cloned parser for the second log file.
            Is there an easy way to clone the GNU/C++ parser without the need of the plugin dev environment?

            hu3b10q7 Csaba Gyorfi added a comment - I have the same issue. In my build project there are two GNU/C++ project and I want to see the results separated, in two graphs. But this is not working as described. As a workaround, it would be nice if I could clone the GNU/C++ parser with a new name, and than use this cloned parser for the second log file. Is there an easy way to clone the GNU/C++ parser without the need of the plugin dev environment?

            People

              drulli Ulli Hafner
              jensger Jens Bohrmann
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: