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

ability to delete parameter-files stuff after a build completes

      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.

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

          First Name added a comment -

          I'm also seeing stuff being accumulated in builds/$buildid/fileParameters/ subdir.

          First Name added a comment - I'm also seeing stuff being accumulated in builds/$buildid/fileParameters/ subdir.

          Xie Shiquan added a comment -

          Voting for a way to delete/manage files in fileParameters subdirectory in the Jobs folder.

          My current build process involves uploading a 300+MB installer file to Jenkins, which would then be deployed on whichever node that is running the build to test the installer file. The file would be cleared from the respective workspaces at the end of the job, but the uploaded file stays in the fileParameters folder, which bulks up the Jenkins directory considerably over time.

          These files will never be used again after the job is done, so there isn't much point in keeping these in the Jobs folder. The installers can be rebuilt at anytime in the future since the file version information is already extracted during build.

          Xie Shiquan added a comment - Voting for a way to delete/manage files in fileParameters subdirectory in the Jobs folder. My current build process involves uploading a 300+MB installer file to Jenkins, which would then be deployed on whichever node that is running the build to test the installer file. The file would be cleared from the respective workspaces at the end of the job, but the uploaded file stays in the fileParameters folder, which bulks up the Jenkins directory considerably over time. These files will never be used again after the job is done, so there isn't much point in keeping these in the Jobs folder. The installers can be rebuilt at anytime in the future since the file version information is already extracted during build.

            huybrechts huybrechts
            userid First Name
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: