Cleanup /tmp dir after execution

[robachmann]

Copied here as requested: openzipkin/zipkin-dependencies#116 (comment)

I know the job is intended as a one-off-task.
However, I deploy the docker image with the following command to make it run the job every 15min:

command: "mv /etc/periodic/hourly/zipkin-dependencies-today /etc/periodic/15min/ && sh -c 'crond -f'"

this worked great for about 3 months. Unfortunately, the respective container in Cloud Foundry recently crashed with an out-of-diskspace exception.

Restaging the container and getting an empty filesystem again, I run this command and receive files that were created in the past 30min:

bash-4.4# find / -type f -mmin -30 | grep -v "proc/" | grep -v "sys/"
find: /proc/tty/driver: Permission denied
/root/.bash_history
/tmp/hsperfdata_root/3013
/tmp/spark-4c962487-6949-4e86-b1fc-ebb1db65029f/userFiles-5ee1f2c2-e98e-43bc-9b54-0153f90a9a37/zipkin-dependencies.jar
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/11/shuffle_1_19_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/11/shuffle_1_13_0.data
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/35/shuffle_1_4_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/35/shuffle_1_13_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/33/shuffle_1_15_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0d/shuffle_1_2_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0a/shuffle_1_5_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0a/shuffle_1_12_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0c/shuffle_1_14_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0c/shuffle_1_3_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0f/shuffle_1_0_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/0f/shuffle_1_17_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/06/shuffle_1_9_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/08/shuffle_1_10_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/08/shuffle_1_7_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/32/shuffle_1_1_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/32/shuffle_1_16_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/37/shuffle_1_6_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/37/shuffle_1_11_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/3e/shuffle_1_9_0.data
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/3c/shuffle_1_7_0.data
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/23/shuffle_1_8_0.data
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/30/shuffle_1_18_0.index
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/13/shuffle_1_11_0.data
/tmp/blockmgr-ec858f88-8f99-4d67-a65c-967ab3d46bbc/39/shuffle_1_8_0.index
/tmp/liblz4-java121974066097708564.so

It seems the job creates those files but won't delete them upon completion.
Would it be possible to have the files deleted as a last step of the job-execution?

That would be very nice!