• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: parameterized-trigger-plugin
• Labels:

  None

[JENKINS-40677] ability to delete parameter-files stuff after a build completes

First Name created issue - 2016-12-26 15:09

First Name made changes - 2016-12-26 15:10

Description

Original: When a parameter is a file, for ex., in "For every matching file, invoke one build", those files are being saved into /var/lib/jenkins/jobs/$job/builds/$buildid/$varname/$file_pattern location. I haven't found any way to delete that stuff from that location -- delete workspace will act on /var/lib/jenkins/workspace/ and "Discard old builds" -> artifacts cleanup checkbox does nothing. Thanks.

New: When a parameter is a file, for ex., in "For every matching file, invoke one build", those files are being saved into /var/lib/jenkins/jobs/$job/builds/$buildid/$varname/$file_pattern location. I haven't found any way to delete that stuff from that location -- "Delete workspace" will act on /var/lib/jenkins/workspace/ and "Discard old builds" -> artifacts cleanup checkbox does nothing. Thanks.

First Name made changes - 2016-12-26 15:10

Description

Original: When a parameter is a file, for ex., in "For every matching file, invoke one build", those files are being saved into /var/lib/jenkins/jobs/$job/builds/$buildid/$varname/$file_pattern location. I haven't found any way to delete that stuff from that location -- "Delete workspace" will act on /var/lib/jenkins/workspace/ and "Discard old builds" -> artifacts cleanup checkbox does nothing. Thanks.

New: When a parameter is a file, for ex., in "For every matching file, invoke one build", those files are being saved into /var/lib/jenkins/jobs/$job/builds/$buildid/$varname/$file_pattern location. I haven't found any way to delete that stuff from that location -- "Delete workspace" will act on /var/lib/jenkins/workspace/ and "Discard old builds" -> "artifacts cleanup" checkbox does nothing. Thanks.