https://bugzilla.wikimedia.org/show_bug.cgi?id=72011
Bug ID: 72011
Summary: Jenkins: Figure out long term solution for /tmp
management
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: Unprioritized
Component: Continuous integration
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Web browser: ---
Mobile Platform: ---
While the VM testing will make this problem obsolete, depending on how far away
this is, this is a high priority problem.
There are various kind of jobs, programs, utilities and other scripts run
inside a Jenkins job that may produce output in /tmp. In some cases this is
configurable and can be disabled. In other cases, it's just an artefact of a
lower level program and really not feasible (nor reasonable) to make this
configurable.
We shouldn't keep /tmp around for ever.
I propose one or both of:
1) Set the $TMPDIR environmental variable to something that is cleaned up.
1a) Dedicated to the job. E.g. some Jenkins plugin that runs globally on all
jobs and nukes the tmp dir after the job is run.
1b) Dedicated to jenkins-slave. E.g. some generic /tmp/jenkins-slave dir that
is purged by a cronjob we run on all contint slaves that will rm-rf items older
than 6 hours.
2) Purge everything in /tmp older than 24 hours.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
