Hacker News new | ask | show | jobs
by pilom 3843 days ago
We do at my work. It has much more robust options. You can keep multiple jobs from running at the same time if one takes too long. You can auto kill it after a time limit. You get a web UI for all logging from the job. You get great built in tools for auto deleting logs after a certain number of builds or time period. You get a very robust email solution for sending out alerts when jobs run or don't run or fail. It adds some complexity vs CRON but it has many more features.
1 comments

it uses a huge amount of resources compared to cron, though, which is my biggest problem with this approach.