CLI option to validate jobfiles

[lurkie]

Today, we ran into an issue where a developer of our team entered an invalid time pattern, preventing our jobber container to start. Thinking about how to prevent this kind of errors in the future, I thought about validating the jobfile during CI without running the jobfile. Is such an option available? If not, please consider this a feature request.

[Pigpocket]

You can do this with jobber test [JOB NAME] when inside a container's runtime terminal /bin/sh

[lurkie]

Thanks for the suggesting. I've tried it today, with this result:

$ jobber test CronCleanupSessions
Running job "CronCleanupSessions"...
Jobber doesn't seem to be running for user $ME.
(No socket at /var/jobber/$UID/cmd.sock.): stat /var/jobber/$UID/cmd.sock: no such file or directory

Jobber is not running yet, as we want it to be during the CI build. jobber test would only be usable when the container has been deployed, but I want to prevent deploying an invalid Yaml file. An option to validate a Yaml file syntactically and semantically without an active daemon would still be desirable.