ess / cronenberg Goto Github PK

Standard cron implementations nuke any environment variables that are set within their running shell. We want to do the opposite. If FOO=bar is set in the shell that launches cronenberg, we want jobs to receive FOO=bar.

Cronenberg always logs to STDOUT. We should also be able to specify a file to which logs should be written (in addition to STDOUT).

The directory tree (dirname) for the file must exist and must be writable by the user that executes cronenberg.

Given a valid job with env vars specified in a jobs file, when I pass that jobs file to cronenberg, the job should be run on its schedule, and the env vars configured for the job should be present. Also, job-scoped env vars take precedence over those specified in the calling environment.

Consider the following job:

- name: env-test
  command: echo $FOO
  when: "* * * * *"
  env:
    FOO: bar-job

Whether or not the shell from which cronenberg is launched has a FOO variable set, the output of this job should be "bar-job"

Provided a valid locking job in a jobs file, when I pass that job file to cronenberg, the job in question should be loaded and executed on the proper schedule, but only one instance of the job should be allowed to run at any given time. Attempts to run a locking job while another instance of the job already exists result in a message that the job is already running and/or is locked.

Provided a valid job in a jobs file, when I pass that job file to cronenberg, the job in question should be loaded and executed on the proper schedule.