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

upload_*.tmp files in /tmp of master cannot be correlated to their specific job and build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Jenkins v1.612, CentOS 6, java version 1.7.0_71

      Attaching a large file (e.g. 300mb) via POST to http://jenkinsserver/job/job_name/buildWithParameters url creates upload_*.tmp files in /tmp directory of the master. These are not deleted automatically after their corresponding builds are completed or cancelled (if in queue). This causes disk space issues in our environment.

      I think it would be better if there is a way to correlate the upload_*.tmp files to their corresponding job_name and queue_id (or any other persistent id) so that there's an easy but intelligent way to clean-up these files (e.g. using post-build). Currently these files can be cleaned up manually (risky for queued jobs) or by rebooting Jenkins server.

          [JENKINS-29121] upload_*.tmp files in /tmp of master cannot be correlated to their specific job and build

          Christopher Orr added a comment -

          This is a duplicate of JENKINS-12699.

          As per that issue, it would be simpler to ensure that Jenkins deletes these temporary files automatically, rather than providing some complex mechanism to allow people to perhaps delete them later.

          Christopher Orr added a comment - This is a duplicate of JENKINS-12699 . As per that issue, it would be simpler to ensure that Jenkins deletes these temporary files automatically, rather than providing some complex mechanism to allow people to perhaps delete them later.

            Unassigned Unassigned
            toshee2000 Elgin Peteza
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: