cucumber-trends.json directory retention

[DanielSchulzeXOM]

What feature do you want to see added?

Currently the cucumber-trends.json file is located at Jenkins job level and the json file is deleted at some point (by this plugin or jenkins?), but the directory cucumber-reports_<alphanumerical numbers> stays forever. If the plugin handles the cleanup of the trends json file, i would like to request to delete the (empty) directory, too. Otherwise, as it is right now, the Jenkins job directory is cluttered with empty directories.
I already cleaned the Jenkins job directory, so i have no exact data which was the oldest cucumber_reports directory, but at least older than 1 year.

Upstream changes

No response

[damianszczepanik]

Trends are stored in location that is accessible from all builds for given project. Trends file lives as long as the project

[DanielSchulzeXOM]

Then what stands "trendsLimit" for? From my point of understanding that should be the limit of builds including in the trend graph. So why keep the data from the older builds and clutter up the hard drive, when they are not part of the report anymore?

But ok, we decided to disable the trends feature, because it is not working for us (with the 2 reports per build issue), but i recognized that still the cucumber-reports_... directory is created (empty) in the Jenkins job main directory. Could this at least be prevented to keep the directory clean?

[damianszczepanik]

Based on the code https://github.com/damianszczepanik/cucumber-reporting/blob/master/src/main/java/net/masterthought/cucumber/ReportBuilder.java#L214-L217 file with the limit is stored as long as the project lives but older data are rotated