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

Add option to not store affected files

Change By:	Ulli Hafner
Summary:	Add option to not store affected files -with-issues folders excessively large
Issue Type:	Bug Improvement

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.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ullrich.hafner@gmail.com (JIRA)

unread,

Jul 18, 2019, 10:08:02 AM7/18/19

to jenkinsc...@googlegroups.com

Ulli Hafner assigned an issue to Unassigned

Jenkins /

Add option to not store affected files

Change By:	Ulli Hafner
Labels:	help-wanted newbie-friendly
Assignee:	Ulli Hafner

ullrich.hafner@gmail.com (JIRA)

unread,

Sep 20, 2019, 4:53:02 AM9/20/19

to jenkinsc...@googlegroups.com

Ulli Hafner commented on

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

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

sladynnunes98@gmail.com (JIRA)

unread,

Mar 16, 2020, 3:01:03 AM3/16/20

to jenkinsc...@googlegroups.com

Sladyn Nunes commented on

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

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

ullrich.hafner@gmail.com (JIRA)

unread,

Mar 16, 2020, 5:35:03 AM3/16/20

to jenkinsc...@googlegroups.com

Ulli Hafner commented on

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...

sladynnunes98@gmail.com (JIRA)

unread,

Mar 16, 2020, 7:00:02 AM3/16/20

to jenkinsc...@googlegroups.com

Sladyn Nunes commented on

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.