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

Provide report filename as variable to Groovy parser

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Fixed
    • warnings-plugin
    • None
    • jenkins 1.504 + warning plug-in 4.35
    • 5.0.0-beta3

    Description

      When using Warning plug-in for parsing several files like *.rpt I would like to be able to display the name of the file being scanned as a category or something else.

      is is possible to catch the filename of the file being scanned in the groovy script of the plugin configuration ?

      for instance :

      test1.rpt contains : "error 1 warning 3"

      test2.rpt contains : "error 10 warning 32"

      test3.rpt contains : "error 132 warning 33"

      And I would like to be able in the parser to catch these lines but including the filename that contains the line. is it something possible ?

      I'm in the case where I don't scan the console but several files.

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          This is not yet possible, the filename is not part of the API. All methods currently work on input streams that do not have a filename anymore.

          drulli Ulli Hafner added a comment - This is not yet possible, the filename is not part of the API. All methods currently work on input streams that do not have a filename anymore.
          iostrym iostrym added a comment -

          thanks for your answer. but i'm not sure to understand what you mean by:

          "all methods currently work on input streams that do not have a filename anymore."

           

          what would be the correct solution to parse a folder that contains N test report like report_test_*.rpt, one for each test ? if I want to know which test generate which error ? use another plug-in maybe ? is there one that would do the job ?

          iostrym iostrym added a comment - thanks for your answer. but i'm not sure to understand what you mean by: "all methods currently work on input streams that do not have a filename anymore."   what would be the correct solution to parse a folder that contains N test report like report_test_*.rpt, one for each test ? if I want to know which test generate which error ? use another plug-in maybe ? is there one that would do the job ?
          drulli Ulli Hafner added a comment -

          This is a internal design decision of my plugin. I'm first finding all files that should be parsed using the filenames. Then I open these files and apply the specified parsers. But each parser has a InputStream as parameter and not a File, so the filename is not known in this class. This needs to be redone to provide a solution for your issue.

          drulli Ulli Hafner added a comment - This is a internal design decision of my plugin. I'm first finding all files that should be parsed using the filenames. Then I open these files and apply the specified parsers. But each parser has a InputStream as parameter and not a File, so the filename is not known in this class. This needs to be redone to provide a solution for your issue.
          iostrym iostrym added a comment -

          ok I understand better. do you know if another plug-in parser could do the job ?

          in FPGA developpement we have often the following case for FPGA Simulation :

          each test has its own simulation report. filename of the report indicate the testname. Also inside the report we could parse the filename of the test (not easy but it can be done) => I don't think also that it could be possible to group all warning below the "test name" warning to be grouped in the same "test group", right ?

           

          for instance :

          test1.rpt : 

          XXXXXX TEST1 XXXXX => parsed correctly => = warning1

          XXXXX warning XXXX => parsed correctly => = warning2

          XXXXX error XXXXX => parsed correctly => = warning3

          => could it be possible to "display" that warning 2 and 3 are related to TEST1 that was parsed in warning1 ? I don't think that warning plugin could work that way... but as it is possible to do several stuf in groovy script, I don't know...

           

          what we don't have for simulation :

          XXXX test1 warning XXXXX

          XXXXX test2 warning XXXXX

          xxxxxxx test2 error XXXXXX

           

          by the way for synthesis it works correctly because the process of synthesis works like a SW compilation : we have a warning that indicates de corresponding file that have problem.

           

           

          iostrym iostrym added a comment - ok I understand better. do you know if another plug-in parser could do the job ? in FPGA developpement we have often the following case for FPGA Simulation : each test has its own simulation report. filename of the report indicate the testname. Also inside the report we could parse the filename of the test (not easy but it can be done) => I don't think also that it could be possible to group all warning below the "test name" warning to be grouped in the same "test group", right ?   for instance : test1.rpt :  XXXXXX TEST1 XXXXX => parsed correctly => = warning1 XXXXX warning XXXX => parsed correctly => = warning2 XXXXX error XXXXX => parsed correctly => = warning3 => could it be possible to "display" that warning 2 and 3 are related to TEST1 that was parsed in warning1 ? I don't think that warning plugin could work that way... but as it is possible to do several stuf in groovy script, I don't know...   what we don't have for simulation : XXXX test1 warning XXXXX XXXXX test2 warning XXXXX xxxxxxx test2 error XXXXXX   by the way for synthesis it works correctly because the process of synthesis works like a SW compilation : we have a warning that indicates de corresponding file that have problem.    
          iostrym iostrym added a comment -

          I'm not well aware of jenkins support. do you think I need to report a more general question, not dedicated to the warning plug-in ?

          to ask if another parser could do the job ? 

          if yes, where can this be asked ? because it seems dedicated to real bug report here, right ?

          iostrym iostrym added a comment - I'm not well aware of jenkins support. do you think I need to report a more general question, not dedicated to the warning plug-in ? to ask if another parser could do the job ?  if yes, where can this be asked ? because it seems dedicated to real bug report here, right ?
          drulli Ulli Hafner added a comment -

          I don't think that there is support for your requirements in another plug-in. So it might be the correct place here. Maybe it makes sense to write a custom parser or extend the plugin to support these requirements directly. Or you can check if you can write some shell scripts that run before the parser: these might create new files that contain this information.

          drulli Ulli Hafner added a comment - I don't think that there is support for your requirements in another plug-in. So it might be the correct place here. Maybe it makes sense to write a custom parser or extend the plugin to support these requirements directly. Or you can check if you can write some shell scripts that run before the parser: these might create new files that contain this information.
          iostrym iostrym added a comment -

          Thanks a lot for your feedback. I'm quite surprised that SW guys don't have this kind of report file to parse. One report per test should be something quite common.

          And in the error/warning message of one test, it is quite "heavy" to write down the name of the TEST each time.

          Or I miss something...

           

          Anyway if the plugin could be improved so that a variable could be used in the groovy script to have the name of the file being parser, it would be awesome ! (and I would be happy to be beta-tester  )

          iostrym iostrym added a comment - Thanks a lot for your feedback. I'm quite surprised that SW guys don't have this kind of report file to parse. One report per test should be something quite common. And in the error/warning message of one test, it is quite "heavy" to write down the name of the TEST each time. Or I miss something...   Anyway if the plugin could be improved so that a variable could be used in the groovy script to have the name of the file being parser, it would be awesome ! (and I would be happy to be beta-tester  )
          iostrym iostrym added a comment -

          Do you know if the enhancement proposed an heavy modification of your plug-in or is it a small add-on ?

          iostrym iostrym added a comment - Do you know if the enhancement proposed an heavy modification of your plug-in or is it a small add-on ?
          drulli Ulli Hafner added a comment -

          I think this is a rather small change (but it will change the API though).

          drulli Ulli Hafner added a comment - I think this is a rather small change (but it will change the API though).
          iostrym iostrym added a comment -

          thanks for your answer. Then do you think this could be added in a future version of the plugin ? < 1 year ? > 1 year ?

           

          or not sure at all that it could be added in the plugin ?

          iostrym iostrym added a comment - thanks for your answer. Then do you think this could be added in a future version of the plugin ? < 1 year ? > 1 year ?   or not sure at all that it could be added in the plugin ?
          drulli Ulli Hafner added a comment -

          < 1 year. But not before the white mountains release is done, see JENKINS-49911.

          drulli Ulli Hafner added a comment - < 1 year. But not before the white mountains release is done, see JENKINS-49911 .
          drulli Ulli Hafner added a comment -

          As a first step I added the file name to the parser API. This needs to be applied to the Groovy part in the Jenkins Plugin as well.

          drulli Ulli Hafner added a comment - As a first step I added the file name to the parser API . This needs to be applied to the Groovy part in the Jenkins Plugin as well.
          iostrym iostrym added a comment -

          thanks a lot. don't hesitate to provide us a test version if you need help to test it before deployment.

          iostrym iostrym added a comment - thanks a lot. don't hesitate to provide us a test version if you need help to test it before deployment.
          drulli Ulli Hafner added a comment - See https://github.com/jenkinsci/warnings-plugin/tree/5.0
          iostrym iostrym added a comment -

          thanks a lot. I have downloaded provided sources in a zip file. i'm sorry in advance for the newby question but what is the process to install this plugin :

          1 - copy paste of source in a specific folder inside jenkins install directory ?

          2 - use jenkins interface and provide the zip file to let jenkins install it ?

          3 - "compile" sources in a specific file format and then provide the compile file in jenkins interface and let jenkins install it ?

          iostrym iostrym added a comment - thanks a lot. I have downloaded provided sources in a zip file. i'm sorry in advance for the newby question but what is the process to install this plugin : 1 - copy paste of source in a specific folder inside jenkins install directory ? 2 - use jenkins interface and provide the zip file to let jenkins install it ? 3 - "compile" sources in a specific file format and then provide the compile file in jenkins interface and let jenkins install it ?
          drulli Ulli Hafner added a comment -

          No, much simpler: use the provided link in the README to download the latest HPI.

          Note: the format and API of the parsers has changed, so you old parsers will not work!

          drulli Ulli Hafner added a comment - No, much simpler: use the provided link in the README to download the latest HPI. Note: the format and API of the parsers has changed, so you old parsers will not work!
          iostrym iostrym added a comment -

          thanks a lot.

          is there a migration process to retrieve my old parser ? or do I need to do manual copy paste ?

          groovy scripts and regular expression could be conserved from my old parser ?

          iostrym iostrym added a comment - thanks a lot. is there a migration process to retrieve my old parser ? or do I need to do manual copy paste ? groovy scripts and regular expression could be conserved from my old parser ?
          drulli Ulli Hafner added a comment -

          There is no process, see documentation. Best way is to use copy and past and then use the new API. It will not take much time to understand the differences. There are also some examples used in my tests.

          drulli Ulli Hafner added a comment - There is no process, see documentation . Best way is to use copy and past and then use the new API. It will not take much time to understand the differences. There are also some examples used in my tests.
          iostrym iostrym added a comment -

          thanks. but in readme.md file there is a link to the online documentation and I presume that in documentation there is the link for the 5.X warning plugin HPI file but I don't succeed to find it. it maybe something obvious but I don't find it

          iostrym iostrym added a comment - thanks. but in readme.md file there is a link to the online documentation and I presume that in documentation there is the link for the 5.X warning plugin HPI file but I don't succeed to find it. it maybe something obvious but I don't find it
          drulli Ulli Hafner added a comment - - edited

          It's a link in the Jira comment above and in the README (CI badge).

          https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/

          drulli Ulli Hafner added a comment - - edited It's a link in the Jira comment above and in the README (CI badge). https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/
          iostrym iostrym added a comment -

          ok I have download it. (I don't know what is the README (CI badge))

          in order to use the name of the parsed file in my groovy script, do you know what is the keyword to use ? (I don't find a groovy script part in the documentation)

          iostrym iostrym added a comment - ok I have download it. (I don't know what is the README (CI badge)) in order to use the name of the parsed file in my groovy script, do you know what is the keyword to use ? (I don't find a groovy script part in the documentation)
          drulli Ulli Hafner added a comment -

          There is a help icon at the script text field. The name is fileName.

          drulli Ulli Hafner added a comment - There is a help icon at the script text field. The name is fileName .
          iostrym iostrym added a comment - - edited

          thanks a lot. I have installed the downloaded HPI but I still have all my parser in the jenkins configuration.

          plug-in version : 

          is seen as installed in jenkins plugin management.

          I though that I would lost all my parser configuration. Do I miss something ?

          [EDIT] found: old parser are still present (not sure there can be still used) and I need to use : 

          Groovy Based Warnings Parsers

           in administration now to add new parsers.

          iostrym iostrym added a comment - - edited thanks a lot. I have installed the downloaded HPI but I still have all my parser in the jenkins configuration. plug-in version :  5.0.0-SNAPSHOT (private-6eea9648-jenkins) is seen as installed in jenkins plugin management. I though that I would lost all my parser configuration. Do I miss something ? [EDIT] found: old parser are still present (not sure there can be still used) and I need to use :  Groovy Based Warnings Parsers  in administration now to add new parsers.
          iostrym iostrym added a comment -

          I tryied to configure new parser so I start with first one by doing copy paste.

          I the testsection of the groovy script I have now this error message :

          Result of the script is not of type 'Issue': hdf_fcc_as_test~jenkinsCI/DPROC_8.lup,?:ascii:1(0):HIGH,No selection available for directory entry ,Synergy update warning:

          is it because there is something to modify in the groovy script when passing from 4.x to 5.x or is there a dependency error because I need to install or uninstall a plugin in jenkins ? I have jenkins 2.121.2 version.

          • Here is my groovy script :

          import hudson.plugins.warnings.parser.Warning
          import hudson.plugins.analysis.util.model.Priority

          String warningTxt= matcher.group(1)
          String objName= matcher.group(2)
          String prjName= matcher.group(3)
          return new Warning(prjName+"
          "+objName, 0, "Synergy update warning", warningTxt, "", Priority.HIGH)

          • regular expression : 

          Warning[!\s]([^'])'([^'])'.+in project '([^'])

          • example log message: 

          Updating 'hdf_fcc_as_test~jenkinsCI'.
          Replaced 0 object(s), out of 10 examined, in project hdf_fcc_as_test~jenkinsCI.
          Replaced 0 object(s), out of 40 examined, in project hdf_fcc_as_test~jenkinsCI.
          Warning: No candidates found for directory entry DPROC_8.lup:ascii:1. It will be left empty!
          Warning! No selection available for directory entry 'DPROC_8.lup,?:ascii:1' under 'src~2' in project 'hdf_fcc_as_test~jenkinsCI'.
          Warning: No candidates found for directory entry DPROC_7.lup:ascii:1. It will be left empty!
          Warning! No selection available for directory entry 'DPROC_7.lup,?:ascii:1' under 'src~2' in project 'hdf_fcc_as_test~jenkinsCI'.

          • in previous warning plugin version I have following result for the test :
            One warning found
            file name: hdf_fcc_as_test~jenkinsCI/DPROC_8.lup,?:ascii:1
            line number: 0
            priority: Priorité haute
            category:  No selection available for directory entry
            type: Synergy update warning
            message:
          iostrym iostrym added a comment - I tryied to configure new parser so I start with first one by doing copy paste. I the testsection of the groovy script I have now this error message : Result of the script is not of type 'Issue': hdf_fcc_as_test~jenkinsCI/DPROC_8.lup,?:ascii:1(0):HIGH,No selection available for directory entry ,Synergy update warning: is it because there is something to modify in the groovy script when passing from 4.x to 5.x or is there a dependency error because I need to install or uninstall a plugin in jenkins ? I have jenkins 2.121.2 version. Here is my groovy script : import hudson.plugins.warnings.parser.Warning import hudson.plugins.analysis.util.model.Priority String warningTxt= matcher.group(1) String objName= matcher.group(2) String prjName= matcher.group(3) return new Warning(prjName+" "+objName, 0, "Synergy update warning", warningTxt, "", Priority.HIGH) regular expression :  Warning [!\s] ( [^'] )'( [^'] )'.+in project '( [^'] ) example log message:  Updating 'hdf_fcc_as_test~jenkinsCI'. Replaced 0 object(s), out of 10 examined, in project hdf_fcc_as_test~jenkinsCI. Replaced 0 object(s), out of 40 examined, in project hdf_fcc_as_test~jenkinsCI. Warning: No candidates found for directory entry DPROC_8.lup:ascii:1. It will be left empty! Warning! No selection available for directory entry 'DPROC_8.lup,?:ascii:1' under 'src~2' in project 'hdf_fcc_as_test~jenkinsCI'. Warning: No candidates found for directory entry DPROC_7.lup:ascii:1. It will be left empty! Warning! No selection available for directory entry 'DPROC_7.lup,?:ascii:1' under 'src~2' in project 'hdf_fcc_as_test~jenkinsCI'. in previous warning plugin version I have following result for the test : One warning found file name: hdf_fcc_as_test~jenkinsCI/DPROC_8.lup,?:ascii:1 line number: 0 priority: Priorité haute category:  No selection available for directory entry type: Synergy update warning message:
          drulli Ulli Hafner added a comment - - edited

          You did not use the new API. There is an example of the new API in the help. Did you click it?

          Here is an example of a test case:

          import edu.hm.hafner.analysis.Priority
          
          String message = matcher.group(5)
          String category = matcher.group(4)
          Priority priority
          if (category.contains("E")) {
              priority = Priority.NORMAL
          } else {
              priority = Priority.LOW
          }
          
          return builder.setFileName(matcher.group(1))
                  .setLineStart(Integer.parseInt(matcher.group(2)))
                  .setColumnStart(Integer.parseInt(matcher.group(3)))
                  .setCategory(category)
                  .setMessage(message)
                  .setPriority(priority)
                  .build()
          
          drulli Ulli Hafner added a comment - - edited You did not use the new API. There is an example of the new API in the help. Did you click it? Here is an example of a test case: import edu.hm.hafner.analysis.Priority String message = matcher.group(5) String category = matcher.group(4) Priority priority if (category.contains( "E" )) { priority = Priority.NORMAL } else { priority = Priority.LOW } return builder.setFileName(matcher.group(1)) .setLineStart( Integer .parseInt(matcher.group(2))) .setColumnStart( Integer .parseInt(matcher.group(3))) .setCategory(category) .setMessage(message) .setPriority(priority) .build()
          iostrym iostrym added a comment -

          thanks a lot. 

          Following your example I use this corrected groovy script : 

           

          import edu.hm.hafner.analysis.Priority

          String warningTxt= matcher.group(1)
          String objName= matcher.group(2)
          String prjName= matcher.group(3)

          return builder.setFileName(warningTxt)
          .setLineStart(Integer.parseInt(objName))
          .setColumnStart(0)
          .setCategory(prjName)
          .setMessage("")
          .setPriority(Priority.HIGH)
          .build()

           

          and I get the error :

           

          Result of the script is not of type 'Issue': null

          by the way, does .setType() exist ? as in 4.X version ? I don't find in documentation the list of possible .setXXX value ? in help, .setPriority is not mentionned for instance whereas I used it in old API :

          return new Warning(prjName+"
          "+objName, 0, "Synergy update warning", warningTxt, "", Priority.HIGH)

           
           

          iostrym iostrym added a comment - thanks a lot.  Following your example I use this corrected groovy script :    import edu.hm.hafner.analysis.Priority String warningTxt= matcher.group(1) String objName= matcher.group(2) String prjName= matcher.group(3) return builder.setFileName(warningTxt) .setLineStart(Integer.parseInt(objName)) .setColumnStart(0) .setCategory(prjName) .setMessage("") .setPriority(Priority.HIGH) .build()   and I get the error :   Result of the script is not of type 'Issue': null by the way, does .setType() exist ? as in 4.X version ? I don't find in documentation the list of possible .setXXX value ? in help, .setPriority is not mentionned for instance whereas I used it in old API : return new Warning(prjName+" "+objName, 0, "Synergy update warning", warningTxt, "", Priority.HIGH)    
          drulli Ulli Hafner added a comment -

          The old parsers, old actions, and old API will still be available so that people that did not covert their jobs will still see the results!

          drulli Ulli Hafner added a comment - The old parsers, old actions, and old API will still be available so that people that did not covert their jobs will still see the results!
          drulli Ulli Hafner added a comment - - edited

          The type exists yes. The new API is part of the analysis-model project, see IssueBuilder (or Issue).

          Seems that Integer.parseInt(objName) evaluates to null in your case. If I remove that line then your script compiles on my machine.

          drulli Ulli Hafner added a comment - - edited The type exists yes. The new API is part of the analysis-model project, see IssueBuilder (or Issue ). Seems that Integer.parseInt(objName) evaluates to null in your case. If I remove that line then your script compiles on my machine.
          iostrym iostrym added a comment -

          Hello, problems resolved. I started using the new version successfully. But I have a problem with 5.x that I didn't have with 4.x because I'm using the same parser twice for parsing files at different location => two times the same parser used

           

          and then, the plugin don't like it :

           
          java.lang.IllegalStateException: ID testparser is already used by another action: io.jenkins.plugins.analysis.core.views.ResultAction for testparser
          it is a shame because it is handfull to be able to parse different files with the same parser because sometime you have different kind of information to parse the same way.

          iostrym iostrym added a comment - Hello, problems resolved. I started using the new version successfully. But I have a problem with 5.x that I didn't have with 4.x because I'm using the same parser twice for parsing files at different location => two times the same parser used   and then, the plugin don't like it :   java.lang.IllegalStateException: ID testparser is already used by another action: io.jenkins.plugins.analysis.core.views.ResultAction for testparser it is a shame because it is handfull to be able to parse different files with the same parser because sometime you have different kind of information to parse the same way.
          iostrym iostrym added a comment - - edited

          Second problem that is maybe not a problem because I may miss a configuration is that for one parser I have 4 tab : files, categories, types, issues (ok) but for another parser I have only 2 tabs : types and issues. (ko)

           

          In first parser, I can click on "files" tab to have summary per file. that is exactly what I want because in my case : one file parsed = one test so I can see a summary of test result.

           

          But unfortunately in the parser of test result I don't have the 4 tabs, I have only 2 tabs. What is strange is that if I click on "issues" tab I can see that file information is present and should be used to have a "files" tab displayed. Only category information is not displayed because not provided by the parser.

           

           [Edit] there is no problem, it seems that a new tab is added only if different values are found in a column. in my test, there was only one file this is why there is no "files" tab. right ?

          iostrym iostrym added a comment - - edited Second problem that is maybe not a problem because I may miss a configuration is that for one parser I have 4 tab : files, categories, types, issues (ok) but for another parser I have only 2 tabs : types and issues. (ko)   In first parser, I can click on "files" tab to have summary per file. that is exactly what I want because in my case : one file parsed = one test so I can see a summary of test result.   But unfortunately in the parser of test result I don't have the 4 tabs, I have only 2 tabs. What is strange is that if I click on "issues" tab I can see that file information is present and should be used to have a "files" tab displayed. Only category information is not displayed because not provided by the parser.     [Edit] there is no problem, it seems that a new tab is added only if different values are found in a column. in my test, there was only one file this is why there is no "files" tab. right ?
          iostrym iostrym added a comment -

          In brief : problem when a parser is used twice (problem don't exist in 4.x). I'm using the same parser twice for parsing files at different location.

           error message is the following :

           java.lang.IllegalStateException: ID testparser is already used by another action: io.jenkins.plugins.analysis.core.views.ResultAction for testparser
          it is a shame because it is handfull to be able to parse different files with the same parser because sometime you have different kind of information to parse the same way.

          But maybe I may need to write this error in a new case about 5.x version ?

          iostrym iostrym added a comment - In brief : problem when a parser is used twice (problem don't exist in 4.x). I'm using the same parser twice for parsing files at different location.  error message is the following :  java.lang.IllegalStateException: ID testparser is already used by another action: io.jenkins.plugins.analysis.core.views.ResultAction for testparser it is a shame because it is handfull to be able to parse different files with the same parser because sometime you have different kind of information to parse the same way. But maybe I may need to write this error in a new case about 5.x version ?
          drulli Ulli Hafner added a comment -

          Is this a freestyle job or pipeline?

          drulli Ulli Hafner added a comment - Is this a freestyle job or pipeline?
          iostrym iostrym added a comment - - edited

          it is a freestyle job.

           

          in the meanwhile, I have a big problem, I don't know if it is a jenkins one or a plug-in warning one... During lunch my computer reboot abnormally (windows update process). I did a lot of groovy script configuration yesterday (4.x to 5.x migration + bug correction). configuration was saved in jenkins and used in jobs. And now, (after reboot I think), all 5.X parser are lost  is there any chance that they are backuped somewhere in a xml file ? how can this append ? when jenkins configuration is done and saved it is not written directly in a xml file ?

           

          [edit] : some other jenkins modification from yesterday are not lost so it seems it is not a jenkins problem. is seems to be a specific 5.X warning plugin problem as I have lost only 5.X warning parser configuration.

           

          [edit] : when performing a search in jenkins directory I can see my parser name in 

          "C:\Program Files (x86)\Jenkins\hudson.plugins.warnings.WarningsPublisher.xml" but this file contain only parser configuration for 4.X version. Not those for 5.X version that I have lost. I don't see any other file (except those in job configuration/result) in jenkins directory that contain my parser names.

           

           [edit] I have the feeling that the file for configuring 5.X warning plugin parser is hudson.plugins.analysis.core.GlobalSettings.xml but is now a blank file :

          <?xml version='1.1' encoding='UTF-8'?>
          <hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl plugin="analysis-core@1.95">
          <isQuiet>false</isQuiet>
          <failOnCorrupt>false</failOnCorrupt>
          <noAuthors>false</noAuthors>
          </hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl>

           

          for your information yesterday I have used "reload configuration from disk" in jenkins administation. but it was working, parser were not deleted after this action. I used it to reload a job that I had modified using its xml file (to copy parser configuration from one job to another)

           

           

          iostrym iostrym added a comment - - edited it is a freestyle job.   in the meanwhile, I have a big problem, I don't know if it is a jenkins one or a plug-in warning one... During lunch my computer reboot abnormally (windows update process). I did a lot of groovy script configuration yesterday (4.x to 5.x migration + bug correction). configuration was saved in jenkins and used in jobs. And now, (after reboot I think), all 5.X parser are lost  is there any chance that they are backuped somewhere in a xml file ? how can this append ? when jenkins configuration is done and saved it is not written directly in a xml file ?   [edit] : some other jenkins modification from yesterday are not lost so it seems it is not a jenkins problem. is seems to be a specific 5.X warning plugin problem as I have lost only 5.X warning parser configuration.   [edit] : when performing a search in jenkins directory I can see my parser name in  "C:\Program Files (x86)\Jenkins\hudson.plugins.warnings.WarningsPublisher.xml" but this file contain only parser configuration for 4.X version. Not those for 5.X version that I have lost. I don't see any other file (except those in job configuration/result) in jenkins directory that contain my parser names.     [edit] I have the feeling that the file for configuring 5.X warning plugin parser is hudson.plugins.analysis.core.GlobalSettings.xml but is now a blank file : <?xml version='1.1' encoding='UTF-8'?> <hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl plugin="analysis-core@1.95"> <isQuiet>false</isQuiet> <failOnCorrupt>false</failOnCorrupt> <noAuthors>false</noAuthors> </hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl>   for your information yesterday I have used "reload configuration from disk" in jenkins administation. but it was working, parser were not deleted after this action. I used it to reload a job that I had modified using its xml file (to copy parser configuration from one job to another)    
          drulli Ulli Hafner added a comment -

          java.lang.IllegalStateException: ID testparser is already used by another action

          In Freestyle Jobs you cannot use the same parser multiple times (if you do not select the aggregate option). You can specify multiple file patterns using a comma separator, this should prevent the problem. The reason is that each result is accessible using the ID of the parser as URL.

          drulli Ulli Hafner added a comment - java.lang.IllegalStateException: ID testparser is already used by another action In Freestyle Jobs you cannot use the same parser multiple times (if you do not select the aggregate option). You can specify multiple file patterns using a comma separator, this should prevent the problem. The reason is that each result is accessible using the ID of the parser as URL.
          iostrym iostrym added a comment - - edited

          thanks.

          what do you mean by "if you do not select the aggregate option" : is there anyway an option to activate in my job so that I can run the parser two times ? thanks for the proposal with coma separator but problem is that the same parser is used to parse 2 kind of information. one kind of information are final test result. if I use your proposal, the final test result will be mixed with all other low level test so it will be hard to figure quickly if all is OK. Maybe a prefix to add for the parser so that they could be used several time and have a separate URL ?

           

          concerning 5.X parser configuration (groovy script) lost, do you have any idea ? I'm about to rewrite them  and I wanted to know if there is a chance to refind them and worst, if there is a chance that eveything disapear again...

           

          [EDIT] I did a test by re-configuring one parser for 5.X warning plugin. before that I made a backup of jenkins directory. After saving the configuration, I made a diff between current jenkins directory and backuped directory. and there is no differences about 5.X parser configuration. So where should the groovy script of 5.X be stored ? is it a bug of the 5.X version ? 

          in file hudson.plugins.analysis.core.GlobalSettings.xml, there is only this even after adding a new parser : 

          <?xml version='1.1' encoding='UTF-8'?>
          <hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl plugin="analysis-core@1.95">
          <isQuiet>false</isQuiet>
          <failOnCorrupt>false</failOnCorrupt>
          <noAuthors>false</noAuthors>
          </hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl>

           

          [EDIT]Also there is nothing about 5.X parser in hudson.plugins.warnings.WarningsPublisher.xml

          there are only 4.X parser whereas on top of file there is : 

          <?xml version='1.1' encoding='UTF-8'?>
          <hudson.plugins.warnings.WarningsDescriptor plugin="warnings@5.0.0-SNAPSHOT">

          I though that it was because my 5.x parser have same name than 4.x parser but I did a trial with a new 5.X parser with a different name and it is the same :

          no 5.X parser are written in any file of jenkins (I did a complete search)

           

          iostrym iostrym added a comment - - edited thanks. what do you mean by "if you do not select the aggregate option" : is there anyway an option to activate in my job so that I can run the parser two times ? thanks for the proposal with coma separator but problem is that the same parser is used to parse 2 kind of information. one kind of information are final test result. if I use your proposal, the final test result will be mixed with all other low level test so it will be hard to figure quickly if all is OK. Maybe a prefix to add for the parser so that they could be used several time and have a separate URL ?   concerning 5.X parser configuration (groovy script) lost, do you have any idea ? I'm about to rewrite them  and I wanted to know if there is a chance to refind them and worst, if there is a chance that eveything disapear again...   [EDIT] I did a test by re-configuring one parser for 5.X warning plugin. before that I made a backup of jenkins directory. After saving the configuration, I made a diff between current jenkins directory and backuped directory. and there is no differences about 5.X parser configuration. So where should the groovy script of 5.X be stored ? is it a bug of the 5.X version ?  in file hudson.plugins.analysis.core.GlobalSettings.xml, there is only this even after adding a new parser :  <?xml version='1.1' encoding='UTF-8'?> <hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl plugin="analysis-core@1.95"> <isQuiet>false</isQuiet> <failOnCorrupt>false</failOnCorrupt> <noAuthors>false</noAuthors> </hudson.plugins.analysis.core.GlobalSettings_-DescriptorImpl>   [EDIT] Also there is nothing about 5.X parser in hudson.plugins.warnings.WarningsPublisher.xml there are only 4.X parser whereas on top of file there is :  <?xml version='1.1' encoding='UTF-8'?> <hudson.plugins.warnings.WarningsDescriptor plugin="warnings@5.0.0-SNAPSHOT"> I though that it was because my 5.x parser have same name than 4.x parser but I did a trial with a new 5.X parser with a different name and it is the same : no 5.X parser are written in any file of jenkins (I did a complete search)  
          drulli Ulli Hafner added a comment -

          Yes, there seems to be something broken. The save method for the parsers is not called. This should be done automatically...

          drulli Ulli Hafner added a comment - Yes, there seems to be something broken. The save method for the parsers is not called. This should be done automatically...
          drulli Ulli Hafner added a comment - Ok, I fixed it in https://github.com/jenkinsci/warnings-plugin/commit/70f3bf376a51821ac62821406d84944148099d27 , needs 30 minutes to build.
          drulli Ulli Hafner added a comment -

          There are two ways to start the same parser twice:

          • use a comma separated list in the pattern text box
          • enable the check box "Aggregate results"

          Would it make more sense to add ID and name per each parser in the UI? This will bloat up the user interface...

          drulli Ulli Hafner added a comment - There are two ways to start the same parser twice: use a comma separated list in the pattern text box enable the check box "Aggregate results" Would it make more sense to add ID and name per each parser in the UI? This will bloat up the user interface...
          iostrym iostrym added a comment - - edited

          thanks for the fix but in https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/, it seems there is no new build from yesterday. is it normal ?

          or maybe the build is here ?

          https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/master/ but last build here is yesterday at 16:30 so it seems to be not ok also.

           [EDIT]: on master branch, last build is written to be at 16:30 but in main page it is said to be at 18:30... strange. I will try this hpi anyway.

          iostrym iostrym added a comment - - edited thanks for the fix but in https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/,  it seems there is no new build from yesterday. is it normal ? or maybe the build is here ? https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/master/  but last build here is yesterday at 16:30 so it seems to be not ok also.   [EDIT] : on master branch, last build is written to be at 16:30 but in main page it is said to be at 18:30... strange. I will try this hpi anyway.
          drulli Ulli Hafner added a comment - The master branch is the right place: https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/master/changes
          iostrym iostrym added a comment - - edited

          I have a lot of difficulties installing this new version. first 5.x installed after a 4.x without any error. but now installing this new 5.X after a first 5.X lead to several error. so I tryied to uninstall "static analytic" before installing the new 5.x but I get :

           

          java.io.IOException: Warnings Plug-in v5.0.0-SNAPSHOT (private-aa9c7a25-jenkins) failed to load. - analysis-model-api v1.0.0-RC3-SNAPSHOT is missing. To fix, install v1.0.0-RC3-SNAPSHOT or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:655) at hudson.PluginManager.dynamicLoad(PluginManager.java:877) Caused: java.io.IOException: Failed to install warnings plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:887) at hudson.PluginManager.dynamicLoad(PluginManager.java:823) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1889) Caused: java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1893) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112) at java.lang.Thread.run(Unknown Source)

          once, after several restart I succeed to have warning installed but saving still dont work (in which file should new parser be installed ? static analytic or warning xml file ?) so maybe a previous version has been installed insteed.

          do I need to reinstall manually static analytic (whereas it seems that when I want to install 5.X, static analytic is automatically installed from the web) ?

          from the web, static analysis utilities installed is 1.95 whereas it seems I need : analysis-model-api v1.0.0-RC3-SNAPSHOT . Where can I download it ? isn't it included in warning 5.X plugin ?

          other try : unsintall warning, install 4.x warning from jenkins then install 5.X (last built) version but then I still have the message :

           
          Warnings Plug-in version 5.0.0-SNAPSHOT (private-aa9c7a25-jenkins)analysis-model-api v1.0.0-RC3-SNAPSHOT is missing. To fix, install v1.0.0-RC3-SNAPSHOT or later.
          and warning plugin don't appear as installed...
           
          I don't understand... is there something else to install using 5.X from the master branch ? because my first 5.X version correctly installed but with save default came from the 5.0 branch...

           

          [EDIT : 6eea9648 version can be installed but there is a save/load bug and last build from master (aa9c7a25 can not be successfully installed because of provided error message)

          iostrym iostrym added a comment - - edited I have a lot of difficulties installing this new version. first 5.x installed after a 4.x without any error. but now installing this new 5.X after a first 5.X lead to several error. so I tryied to uninstall "static analytic" before installing the new 5.x but I get :   java.io.IOException: Warnings Plug-in v5.0.0-SNAPSHOT (private-aa9c7a25-jenkins) failed to load. - analysis-model-api v1.0.0-RC3-SNAPSHOT is missing. To fix, install v1.0.0-RC3-SNAPSHOT or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:655) at hudson.PluginManager.dynamicLoad(PluginManager.java:877) Caused: java.io.IOException: Failed to install warnings plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:887) at hudson.PluginManager.dynamicLoad(PluginManager.java:823) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1889) Caused: java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1893) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112) at java.lang.Thread.run(Unknown Source) once, after several restart I succeed to have warning installed but saving still dont work (in which file should new parser be installed ? static analytic or warning xml file ?) so maybe a previous version has been installed insteed. do I need to reinstall manually static analytic (whereas it seems that when I want to install 5.X, static analytic is automatically installed from the web) ? from the web, static analysis utilities installed is 1.95 whereas it seems I need : analysis-model-api v1.0.0-RC3-SNAPSHOT . Where can I download it ? isn't it included in warning 5.X plugin ? other try : unsintall warning, install 4.x warning from jenkins then install 5.X (last built) version but then I still have the message :   Warnings Plug-in version 5.0.0-SNAPSHOT (private-aa9c7a25-jenkins)analysis-model-api v1.0.0-RC3-SNAPSHOT is missing. To fix, install v1.0.0-RC3-SNAPSHOT or later. and warning plugin don't appear as installed...   I don't understand... is there something else to install using 5.X from the master branch ? because my first 5.X version correctly installed but with save default came from the 5.0 branch...   [EDIT : 6eea9648 version can be installed but there is a save/load bug and last build from master (aa9c7a25 can not be successfully installed because of provided error message)
          drulli Ulli Hafner added a comment -

          Sorry about that. I'm preparing the actual beta release for the update center and now the plugin requires an additional plugin (analysis-model-api). There is no published version available up to now, I'm waiting for an approval for the permissions request.

          drulli Ulli Hafner added a comment - Sorry about that. I'm preparing the actual beta release for the update center and now the plugin requires an additional plugin ( analysis-model-api ). There is no published version available up to now, I'm waiting for an approval for the permissions request.
          drulli Ulli Hafner added a comment -

          Ok, a new release is on its way: https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/master/

          • I added the possibility to change the name and ID of a tool definition.
          • I removed the plug-in dependency to analysis-model-api
          drulli Ulli Hafner added a comment - Ok, a new release is on its way: https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/master/ I added the possibility to change the name and ID of a tool definition. I removed the plug-in dependency to analysis-model-api
          iostrym iostrym added a comment - - edited

          thanks a lot for the two corrections. 

           

          but after testing build 50 (that is installed correctly this time), I have the following error :

           

          This is not a valid Groovy script: startup failed:
          Script1.groovy: 1: unable to resolve class edu.hm.hafner.analysis.Priority
          @ line 1, column 1.
             import edu.hm.hafner.analysis.Priority

          because of the first line of my groovy script that work on precedent version :

          import edu.hm.hafner.analysis.Priority

           

           [edit] : great this time a file io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.xml is created after saving my job !

           

          [edit2] : ok, in example i need to call 

          import edu.hm.hafner.analysis.Severity

           instead of the other one + severity configuration is also changed. (is it a final choice or will it be re-corrected when other plugin dependency will be redone ?)

          iostrym iostrym added a comment - - edited thanks a lot for the two corrections.    but after testing build 50 (that is installed correctly this time), I have the following error :   This is not a valid Groovy script: startup failed: Script1.groovy: 1: unable to resolve class edu.hm.hafner.analysis.Priority @ line 1, column 1.    import edu.hm.hafner.analysis.Priority because of the first line of my groovy script that work on precedent version : import edu.hm.hafner.analysis.Priority     [edit] : great this time a file io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.xml is created after saving my job !   [edit2] : ok, in example i need to call  import edu.hm.hafner.analysis.Severity  instead of the other one + severity configuration is also changed. (is it a final choice or will it be re-corrected when other plugin dependency will be redone ?)
          iostrym iostrym added a comment -

          Hello, it seems to work correctly. one remark :

          I have now this error message (unreadable data) in top of my jenkins for my two jobs that were configured before doing the 5.X upgrade. passing from 4.X to 5.X didn't generate this message. do you have an idea ? these error are here even after an update. Could I delete this unreadable date because it is an upsolete one ?

          hudson.model.FreeStyleBuild job_name1 #5 MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor'
          iostrym iostrym added a comment - Hello, it seems to work correctly. one remark : I have now this error message (unreadable data) in top of my jenkins for my two jobs that were configured before doing the 5.X upgrade. passing from 4.X to 5.X didn't generate this message. do you have an idea ? these error are here even after an update. Could I delete this unreadable date because it is an upsolete one ? hudson.model.FreeStyleBuild job_name1 #5 MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor', MissingFieldException: No field 'minimumPriority' found in class 'io.jenkins.plugins.analysis.core.quality.HealthDescriptor'
          iostrym iostrym added a comment -

          Hello, concerning the ability to provide filename, it is working perfectly. Just one remark even if I don't know if it could be corrected.

          it is very handfull to be able to open a file that is mentionned in a warning. This is possible using the file "field".

          sometime instead of the mentionned file (because there are no mentionned file), i put in the file field the name of the file being parser. Here again it is perfect because I'm able to open the parsed file at correct line/column and this is very handfull to have the context of an error (previous error message for instance)

          but for some parser I have a file mentionned in a warning and also it could be very handfull to be able to see in the parsed file (or console) when the warning occurs. this could be done with fileName variable. But problem because there is only one "file field" that allow to have a link to a file.

          would it be possible to have second "file field" so that we could have "parsed file" + "mentionned file" links ?

          or maybe simpler, be able to have category or type field to act as a "file field" :

          => when a file is provided in type/category, include a link to it (correct line)

          => when a file is provided in type/category, display only filename and not the path (I already deal this using groovy script)

          => when a file is provided in type/category with a line, consider that filename:X and filename:Y are the same file and not different kind of categories

           

          Your correction provides already a great advance for parsing simulation of FPGA developpement.

          But this last correction would be a nice improvement. don't know if it would break a lot of stuff.

          iostrym iostrym added a comment - Hello, concerning the ability to provide filename, it is working perfectly. Just one remark even if I don't know if it could be corrected. it is very handfull to be able to open a file that is mentionned in a warning. This is possible using the file "field". sometime instead of the mentionned file (because there are no mentionned file), i put in the file field the name of the file being parser. Here again it is perfect because I'm able to open the parsed file at correct line/column and this is very handfull to have the context of an error (previous error message for instance) but for some parser I have a file mentionned in a warning and also it could be very handfull to be able to see in the parsed file (or console) when the warning occurs. this could be done with fileName variable. But problem because there is only one "file field" that allow to have a link to a file. would it be possible to have second "file field" so that we could have "parsed file" + "mentionned file" links ? or maybe simpler, be able to have category or type field to act as a "file field" : => when a file is provided in type/category, include a link to it (correct line) => when a file is provided in type/category, display only filename and not the path (I already deal this using groovy script) => when a file is provided in type/category with a line, consider that filename:X and filename:Y are the same file and not different kind of categories   Your correction provides already a great advance for parsing simulation of FPGA developpement. But this last correction would be a nice improvement. don't know if it would break a lot of stuff.
          drulli Ulli Hafner added a comment -

          Severity is the new name in all of the libraries. You can clean up your job with missing references to priority.

          drulli Ulli Hafner added a comment - Severity is the new name in all of the libraries. You can clean up your job with missing references to priority.
          drulli Ulli Hafner added a comment -

          Second file name property: this makes not much sense for the other tools. Normally you are not interested in the name of the report, the link shows the affected code.

          drulli Ulli Hafner added a comment - Second file name property: this makes not much sense for the other tools. Normally you are not interested in the name of the report, the link shows the affected code.
          iostrym iostrym added a comment -

          thanks: unreadable data delete with success.

          second file name property : suppose you are doing an FPGA synthesis. then there is a warning with path of the source code affected. using your parser I can catch the name of the source file. But it would be great also if I can also link to the complete report at correct line in the report. because often an error is the consequence of one or more warning that written before the error.

          This is why the view of the complete log is usefull. 

          Using your parser and last modification I can do this but then I will loose the affected source code link.

          For testing : no problem your modification is enough because there is no affected code to link with so I can use the report name and line as "file attribute"

          But for synthesis or place&route it could be usefull to have this feature.

          synthesis may be like compilation, it is the same kind of process but for FPGA. I don't remember well how sw compiler generates warning but for synthesis and place&route, very often an error is understood by the presence of warnings before the error.

          iostrym iostrym added a comment - thanks: unreadable data delete with success. second file name property : suppose you are doing an FPGA synthesis. then there is a warning with path of the source code affected. using your parser I can catch the name of the source file. But it would be great also if I can also link to the complete report at correct line in the report. because often an error is the consequence of one or more warning that written before the error. This is why the view of the complete log is usefull.  Using your parser and last modification I can do this but then I will loose the affected source code link. For testing : no problem your modification is enough because there is no affected code to link with so I can use the report name and line as "file attribute" But for synthesis or place&route it could be usefull to have this feature. synthesis may be like compilation, it is the same kind of process but for FPGA. I don't remember well how sw compiler generates warning but for synthesis and place&route, very often an error is understood by the presence of warnings before the error.
          drulli Ulli Hafner added a comment -

          Yes, I understand that this feature makes sense in your case. I think this requires changes in the UI as well, so this cannot be implemented in the Groovy parser component. I think such a feature needs to be implemented in Java (e.g. as a new plug-in that depends on the warnings plugin). The DRY parser does something similar. It creates issues that have references to other source code (the duplications).

          drulli Ulli Hafner added a comment - Yes, I understand that this feature makes sense in your case. I think this requires changes in the UI as well, so this cannot be implemented in the Groovy parser component. I think such a feature needs to be implemented in Java (e.g. as a new plug-in that depends on the warnings plugin). The DRY parser does something similar. It creates issues that have references to other source code (the duplications).
          iostrym iostrym added a comment -

          thanks for your answer. another suggestion : without modification in the UI (what is it ? jenkins core part ?), is it possible to have the category or type field in the groovy script to behave like a file field ? it means that if I put a filename in this field, then when reading result I could be able to click on filename in category/type field and have a link to open the corresponding file ? and the same for the line number in the file

          iostrym iostrym added a comment - thanks for your answer. another suggestion : without modification in the UI (what is it ? jenkins core part ?), is it possible to have the category or type field in the groovy script to behave like a file field ? it means that if I put a filename in this field, then when reading result I could be able to click on filename in category/type field and have a link to open the corresponding file ? and the same for the line number in the file
          drulli Ulli Hafner added a comment -

          No, the file column is hard coded. All other columns navigate into the details of the selected element.

          drulli Ulli Hafner added a comment - No, the file column is hard coded. All other columns navigate into the details of the selected element.
          iostrym iostrym added a comment -

          hello, is it normal that using new plugin, I don't find anymore the choice to parse directly the console output instead of a specific report file ?

          iostrym iostrym added a comment - hello, is it normal that using new plugin, I don't find anymore the choice to parse directly the console output instead of a specific report file ?
          drulli Ulli Hafner added a comment -

          Please use the Gitter channel for questions.

          You still can parse the Console log, just specify no pattern.

          drulli Ulli Hafner added a comment - Please use the Gitter channel for questions. You still can parse the Console log, just specify no pattern.
          iostrym iostrym added a comment -

          Hello,

          Could you please tell me if 5.0 beta version I tried is now available in the official jenkins plugin store ? Is it compatible with the one I installed ?

          sorry, I'm waiting for my company autorize us to use the gitter channel

          best regards,

          iostrym iostrym added a comment - Hello, Could you please tell me if 5.0 beta version I tried is now available in the official jenkins plugin store ? Is it compatible with the one I installed ? sorry, I'm waiting for my company autorize us to use the gitter channel best regards,
          drulli Ulli Hafner added a comment -

          The current version is still in beta and available at the official but experimental update center: https://updates.jenkins.io/experimental/

          drulli Ulli Hafner added a comment - The current version is still in beta and available at the official but experimental update center: https://updates.jenkins.io/experimental/

          People

            drulli Ulli Hafner
            iostrym iostrym
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: