-
Improvement
-
Resolution: Duplicate
-
Major
-
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
Elgin Peteza
created issue -
Elgin Peteza
made changes -
| Description |
Original:
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 way to cleanup these files (e.g. using post-build). |
New:
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. |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 163989 ] | New: JNJira + In-Review [ 197377 ] |