In search of a better job scheduler (opens in new tab)

I don't get the systemd hate in this specific case. Their timers are pretty much the best possible option you have to schedule jobs, hands down. No cron Daemon is ever going to get there due to the lack of deep integration with the rest of the init system.

I know it takes a while to get used to the ini file madness, but honestly, I can't detect so much boilerplate there: every single line in my units and timers makes sense.

If you're not familiar with that system yet, I can only encourage you to at least take a look at systemd timers. They are really cool! :)

Jenkins works reasonably well as a job scheduler. The UI is functional if not pretty, it is fairly easy to configure and use even for a large number of jobs, and the plugin ecosystem allows you to extend it in many ways without writing any code.

Is there a reason not to consider apache airflow? https://airflow.apache.org/

You could run it on a digital ocean droplet so you don't have to worry about your laptop turning off. It covers retry and cron-style job kickoffs.

Anyone have a good open source replacement for Autosys or controlM? Should be easy to replace but every enterprise I've seen still pays for one of those.

I love all the options we have today.

At Cronitor we are seeing a lot of users migrating to Airflow, Kubernetes cron jobs, and scheduled lambdas.

Like databases, different workloads will benefit from different guarantees. Look for the right tool for the job, not the right tool for all time.

You can create systemd timers and services quite easily with NixOS configuration : https://nixos.wiki/wiki/Nix_Cookbook

One more:

Rundeck https://docs.rundeck.com/docs/manual/

I work on a meta scheduler that solves the problem of periodicity on cron - https://cylc.github.io/

It was created to manage weather forecast model runs. The new version which we are working on will have a simpler web GUI to replace its old PyGTK and Py2.

It handles o ly scheduling, and supports cyclic graphs (contrary to most workflow managers build with DAGs only).

No Python API yet, but coming in future release. So only a custom suite.rc INI style file that supports Jinja2 too.

« better specs for jobs

dependencies, timeouts, resource policies and retries without hacky wrappers and boilerplate »

This is what I miss.

There's a strange gap in traditional Unix there, compared to other time-sharing systems. I have a feeling that if Unix had had a primitive job manager then by 1990 there would have been a pile of Gnu extensions and by 2000 there would have been people reinventing it, and GUIs that looked a bit like what you get to monitor print queues.

I know this is mac specific, but since op is looking for personal infra level tooling/scheduling, there might be an equivalent what ical offers:

create ical event+repeat+alert=Custom(Open file)

this will open a file every repeat event. The file can be shell/workflow or whatever you want to run.

I automated the tedious work to create systemd timers in an ansible role: https://yourlabs.io/oss/yourlabs.timer

As a result, I can execute it include it in another ansible role, or use bigsudo to apply it as a one-off command:

    bigsudo yourlabs.timer @somehost name=your-backup cmd=/your/backup.sh oncalendar='*-*-* 00:00:00 Europe/Paris'

I keep wondering whether there's a job scheduler for me too, but not finding much. At work I'm using/writing a custom one: with multiple schedules in crontab format for each task, frequent automated task updates (by an identifier) from multiple sources, additional flags for some jobs to not run if the parameters didn't change, and/or to rerun every few hours to ensure that proper states are set. It still felt like a generic enough task to use an external tool with those requirements, but then additional functionality appeared, such as changing task parameters according to certain rules (and internal state). At this point it seems that the way to go is either a custom scheduler or just regular cron, crontab editing, and wrappers akin to cronic (or otherwise handling the state-related configuration in the tasks it runs) -- that is, also a custom scheduling system, but incorporating cron. Here cron's simplicity seems fine: say, prevention of duplicate tasks should be by those "task group" IDs, rather than just jobs listed in crontab (so even if cron had the latter, it wouldn't be useful).

I'm pretty sure something like Kube could be used to do this using CronJobs, pod affinities, and Prometheus+AlertManager for alerts and notifications.

You can specify memory, CPU, retries, monitor, and run on many computers.

I think Kube is like systemd + cron + containers had a baby.

Slightly tangential but all I could think about while reading this was: Ansible. I switched to it about 6 months back - including for managing e.g. cron jobs and systemd - and I can’t imagine going back to doing any of this by hand. High-level abstraction and jinja2 templating makes this stuff a breeze.

Drone.io for me, simple and dockerized