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

Add option to not store affected files

XMLWordPrintable

      We are using the warnings-ng plugin to analyze some of our projects with the following code

      recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')]

      This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin.

      An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.

          [JENKINS-58167] Add option to not store affected files

          Philipp Moeller created issue -
          Ulli Hafner made changes -
          Description Original: We are using the warnings-ng plugin to analyze some of our projects with the following code
          {code:java}
          recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')]{code}

          This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin.

          An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.

          		 New: We are using the warnings-ng plugin to analyze some of our projects with the following code
          {code:java}
          recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')]
          {code}

          This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin.

          An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Summary Original: files-with-issues folders excessively large New: Add option to not store affected files
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          Labels New: help-wanted newbie-friendly

          Ulli Hafner added a comment -

          Maybe we should provide the same options as the coverage API plugin.

          Ulli Hafner added a comment - Maybe we should provide the same options as the coverage API plugin.

          Sladyn Nunes added a comment -

          drulli I would like to get started with this issue, any pointers on getting started with this ?

          Sladyn Nunes added a comment - drulli I would like to get started with this issue, any pointers on getting started with this ?

          Ulli Hafner added a comment -

          One thing to start with is to have a look at the coverage-api plugin and see which options they provide for the user.

          Then we can discuss if we are heading for the simple solution (boolean flag) or a more sophisticating approach. One question for the latter one is: should this be solved in my plugin? Or should this be part of a source code renderer plugin that handles such a thing for all Jenkins plugins that show source code in some form. I discussed this in the coverage API Gitter channel a couple of weeks ago. I think providing a plugin would definitely be the best way but also the most complex one. I think this would be a GSoC project on its own...

          Ulli Hafner added a comment - One thing to start with is to have a look at the coverage-api plugin and see which options they provide for the user. Then we can discuss if we are heading for the simple solution (boolean flag) or a more sophisticating approach. One question for the latter one is: should this be solved in my plugin? Or should this be part of a source code renderer plugin that handles such a thing for all Jenkins plugins that show source code in some form. I discussed this in the coverage API Gitter channel a couple of weeks ago. I think providing a plugin would definitely be the best way but also the most complex one. I think this would be a GSoC project on its own...

          Sladyn Nunes added a comment -

          Yeah I seen the thread on gitter, well then I guess I should move on to picking another issue, since the scope for the implementation is pretty wide.

          Sladyn Nunes added a comment - Yeah I seen the thread on gitter, well then I guess I should move on to picking another issue, since the scope for the implementation is pretty wide.
          Ulli Hafner made changes -
          Link New: This issue relates to JENKINS-62151 [ JENKINS-62151 ]
          Ulli Hafner made changes -
          Epic Link New: JENKINS-62153 [ 206075 ]

          Roman Zwi added a comment -

          Quick workaround that worked for me:
          Configure a custom groovy parser that doesn't set the filename.
          So Warnings NG doesn't know the file name and can't do anything about it (this also avoids NoSuchFileException issues).

          Roman Zwi added a comment - Quick workaround that worked for me: Configure a custom groovy parser that doesn't set the filename. So Warnings NG doesn't know the file name and can't do anything about it (this also avoids NoSuchFileException issues).

            drulli Ulli Hafner
            pmr Philipp Moeller
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: