From e5ada4899a74d916d8e661edd7758e5950b8e009 Mon Sep 17 00:00:00 2001 From: Thomas Levine <_@thomaslevine.com> Date: Fri, 26 Feb 2016 15:57:21 +0000 Subject: [PATCH] task runner ideas --- TODO | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/TODO b/TODO index 26d32b4..6dacb80 100644 --- a/TODO +++ b/TODO @@ -145,3 +145,15 @@ on the nvm tests. I wound up running this instead. The Molly guard would be assessed, and the corresponding setup, setup_dir, teardown, and teardown_dir files would be run in the appropriate order. + +Running automated tasks +------------------------- +Urchin might be appropriate for if you have lots of tasks that you want to run +periodically; add an urchin call to your crontab, and call all of your other +tasks with urchin. Here are some features that might make urchin better for +this sort of thing. + +* Time how long each test/job takes +* Optionally kill tests/jobs after a specific timeout threshold +* Send output of different tests/jobs to different files for each file + descriptor (STDOUT, STDERR)