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

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

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-plugin
    • Windows 2003 Server, Jenkins 1.522 Warnings 4.26
    • 5.0.0-beta2

      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.

          [JENKINS-18708] Make it possible to have several files as input for one parser

          Jens Bohrmann created issue -

          Ulli Hafner added a comment -

          This is not supported yet. As a workaround you need to define a file pattern that matches all of your files.

          Ulli Hafner added a comment - This is not supported yet. As a workaround you need to define a file pattern that matches all of your files.
          Ulli Hafner made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Ulli Hafner made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]

          Ulli Hafner added a comment -

          What is the expected output in this case? Three results (graphs etc.) or one result?

          Ulli Hafner added a comment - What is the expected output in this case? Three results (graphs etc.) or one result?

          Jens Bohrmann added a comment -

          I would expect three results since I have three different doxygen projects and I run doxygen three times.

          Jens Bohrmann added a comment - I would expect three results since I have three different doxygen projects and I run doxygen three times.
          Ulli Hafner made changes -
          Summary Original: Warnings-Plugin could not distinguish multiple doxygen warning files. New: Make it possible to have several files as input for one parser
          Ulli Hafner made changes -
          Link New: This issue is duplicated by JENKINS-22653 [ JENKINS-22653 ]

          Similar issue in JENKINS-22653, with one difference:
          Plugin does not mix/merge the warnings but instead shows only the warnings from the file or log that was parsed most recently.

          Thomas Ellinger added a comment - Similar issue in JENKINS-22653 , with one difference: Plugin does not mix/merge the warnings but instead shows only the warnings from the file or log that was parsed most recently.

          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?

          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?

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

              Created:
              Updated:
              Resolved: