Cron jobs have a funny way of being ignored. Either no one knows the job is failing because the job doesn’t tell anyone. Or, the job is spamming your e-mail inbox many times a day, regardless of success or failure, which means you just ignore the e-mails.
I’ve seen the “Monitor an external job” option for new Jenkins jobs before, and never paid much attention. Turns out it’s a great bucket for storing logs and results of cron jobs.
The external-monitor-job plugin seems to ship with the Jenkins war file. So, your Jenkins should have it out of the box.
Creating a job is pretty simple. It’s just a name and description. Click “New Item” in Jenkins and
select the “Monitor an external job” option. This creates a job of type
The wiki describes a fairly complicated method to download the Jenkins jar files onto the server running your cron jobs, and then use the Java runtime to run a jar with your cron script as an argument. The jar presumably forks your a new shell to run your desired cron command and sends the output/result to Jenkins.
There’s a much easier way to do this. Redirect or
tee your job’s stdout/stderr output to a
temp file. Then post the result code and log file via
curl to Jenkins. No need to
download jar files. No need to even have Java runtime on the server.
Just POST a small XML document with the log contents (binary encoded) and the
exit code to Jenkins @
:jobName is the
URL encoded name of your monitoring job in Jenkins.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
A sample of the build log on Jenkins with a green/red build status:
Credit to Taytay on Stackoverflow.com
for figuring out how to use
hexdump to properly encode the XML for Jenkins.