Allow batches 30s of cleanup time on external kills

docs/source/jobs.rst

@@ -395,6 +395,13 @@ AM).
 
 Cleanup Actions
 ---------------
+There are two possible approaches for cleanup that will depend on when you'd
+like the cleanup to occur. You can either:
+* Configure your code to cleanup on recieving a SIGTERM (NOTE: we have a
+  hardcoded limit of 30s before we send a SIGKILL and force-kill the action)
+  to handle cleanup whenever Tron or a human decides to tronctl kill a run
+* OR, use a cleanup action as detailed below to handle cleanup after a job run
+  has completed.
 
 Cleanup actions run after the job succeeds or fails. They are specified just
 like regular actions except that there is only one per job and it has no name

requirements-minimal.txt

@@ -21,7 +21,7 @@ pytimeparse
 pytz
 PyYAML>=5.1
 requests
-task_processing[mesos_executor,k8s]>=1.1.0
+task_processing[mesos_executor,k8s]>=1.2.0
 Twisted>=19.7.0
 urllib3>=1.24.2
 Werkzeug>=0.15.3

requirements.txt

@@ -80,7 +80,7 @@ setuptools==65.5.1
 six==1.15.0
 sshpubkeys==3.1.0
 stack-data==0.6.2
-task-processing==1.1.0
+task-processing==1.2.0
 traitlets==5.0.0
 Twisted==22.10.0
 typing-extensions==4.5.0