[barkmadley]

You can implement crons level of timing specificity with a few "every" jobs and some variables.

e.g. (not real syntax)

    every minute: set minute = (minute + 1) % 60

    when minute = 4 && day = 5 ...

I think the better part of this system is the cascading success semantics that it would provide, where by a next stage doesn't start if the previous stage didn't finish successfully. This has a lot of overlap with Jenkins and other CI servers, but without the java/http overhead and with a (potentially) lighter weight text based syntax for specifying the dependencies between jobs.

I can even envision this sort of system to be used to distribute jobs to slave machines given a small amount of ssh foo.