Package: job-runner
Job-Runneris a crontab like tool, with a nice web-frontend for
administration and (live) monitoring the current status.Features:Schedule recurring jobsChaining of jobsLoad-balance workers by putting them in a poolSchedule jobs to run on all workers within a poolLive dashboard (with option to kill runs and ad-hoc scheduling)Multiple projects and per-project permission managementThe whole project consists of three separate components (and repositories):Job-Runner: provides the REST interface, admin interface and (live)
dashboard. As well this component provides a long-running process
(manage.py broadcast_queue) to broadcast messages (over ZeroMQ) to the
workers. See:https://github.com/spilgames/job-runnerJob-Runner Worker: the process that is responsible for executing the job.
It subscribes to (ZeroMQ) messages coming frombroadcast_queue, send data
back over the REST interface and publishes events to theJob-Runner WebSocket Server.
You can run as many workers as you like, as long as every worker has it’s own
API key (eg: when you want to run jobs on multiple servers or under different
usernames on the same server). API keys can be created in theJob-Runneradmin interface.
See:https://github.com/spilgames/job-runner-workerJob-Runner WebSocket Server: will subscribe toJob-Runner Workerevents
and re-broadcast them to WebSocket connections coming from theJob-Runnerdashboard. This makes it possible to add realtime monitoring to the
dashboard.
See:https://github.com/spilgames/job-runner-ws-serverLinksdocumentationjob-runner sourcejob-runner-worker sourcejob-runner-ws-server sourceChangesv3.5.2Added more logging (notifications) and fixed minor logging issuesv3.5.1Add logging about scheduling, job kills and general failuresv3.5.0Add support for filtering ontitlein the API.Add support for updating and creating jobs in the API.v3.4.0Addworker_versionandconcurrent_jobsfields to the Worker resource.
These fields will be send by the worker at every ping response and are
displayed in the admin.v3.3.0Handle error response when the user does not have access anymore to the
worker data in the REST API. This can happen when a worker is removed from a
worker-pool.Show the full job-chain on the jobs page.Add check to assure that there is no recursion in the job-chain
(parent/child relations).v3.2.0Make it possible to continue the chain of jobs when one of the jobs failed
(or when a worker failed when run on all workers is selected).Add management-commandhealth_checkwhich marks runs assigned to
unresponsive workers as failed and alert when all workers within a pool
are unresponsive.Fixorder_byinreschedulemethod.v3.1.3Redirect to the last selected project (failing that, to the first project
in the list).v3.1.2Fix: do not schedule disabled children (regression introduced by the new
way of scheduling in v3.1.0).v3.1.1Markdown support for job descriptions was added.Scheduled runs are now displayed in the job details.Improve performance by increasing the default API page-size to 200.Show the user a warning when there are no projects.v3.1.0WarningBefore deploying this version, make sure that there aren’t any
running jobs! One way to do this is to disable all projects in the
admin, let all runs complete, and then upgrade.Schedule the next run before broadcasting the current scheduled run.Remove “after complete dts” reschedule option.v3.0.3Make sure to rollback transaction in case of an exception inbroadcast_queuemanagement command.Fix issue with “run on all workers” jobs, where it wasn’t detected that
all siblings finished.v3.0.2Apply “Save as new” button to all model admins.Fix validation of the reschedule interval field (should not accept 0).Add dropdown option to see the runs / jobs of all projects.Show assigned workers in last 100 completed runs.Thebroadcast_queuecommand is now locking the selected runs. This is
needed to make sure that when there are multiple broadcasters, no duplicated
runs are generated (in case of run on all workers).v3.0.1Fix re-schedule issue (duplicates) when manually schedule a recurring job.Fix schedule-time when switching from or to daylight saving-time. Before
the time of a job would change when switching from or to DST. Now a job
will be always re-scheduled at the same time (when increment schedule dts by
interval is selected).v3.0.0New dashboard layout to make it more easy to view large sets of data.Optimization of the initial load of data (fewer API requests).Add support to run a job across all workers within a worker-pool.v2.0.1Optimize the way how theModelAuthorizationclass is testing if the user
or worker has access to the object.v2.0.0Restructure the relations between models. Workers are now project independent
and are grouped by pools. Permissions are now managed on project level
(instead on project and job-template level) By assigning a job to a pool
containing multiple workers, the job will be loadbalanced
(by selecting a random worker).After upgrading, make sure to runmanage.py migrateto migrate your
data to the new structure.WarningBefore runningmanage.py migrate, make a backup of your
data! The new structure is not backwards compatible and
thus can not be migrated backwards.v1.4.3Fix duplicated enqueues when the worker is down or the enqueue is disabled
for the job. This happened for example when a parent-job tried to schedule
a child job which was disabled.v1.4.2Fix the issue where runs from other projects than the selected one, were
rendered on the dashboard.v1.4.1Add caching of objects to improve the performance (frontend).v1.4.0Complete refactor of front-end code. The front-end is now based on AngularJS.Misc admin interface improvements (sorting, labels, etc…).Add if the run was manual and / or killed to the error e-mail template.Add compressor for JavaScript code.v1.3.3Broadcast ping requests to the worker (default: every 5 minutes) and show
last ping response in admin. This will make it more easy to discover problems
with workers.v1.3.2Spil specific settings removed.v1.3.1Fix run status modal JavaScript code (was not working when there is no log
yet).Fix related name ofrun_log, to make sure it shows up correctly in the
template when there is an error.v1.3.0Move logs to separate model and RESTful resource. Make sure that you update
the worker to >= v1.1.0.v1.2.10Show full path (project - template - worker …) in object title.Improve ordering of objects in the admin.Added getting started section to the docs.Misc documentation improvements.v1.2.9Fix kill button so that it is only visible when the user has permission to
kill a job-run (would else result in a HTTP error).v1.2.8Add option in dashboard to kill job-runs.Fix time-zone in failed-run e-mail template (will now use the time-zone
configured in the Django config).v1.2.7Disable the job when it failed more than x times (optional setting).v1.2.6Make it possible to disable the enqueue of a project, worker or job-template.v1.2.5Display parent - child relationships in job details.Fix an other issue with the run broadcaster to make sure it doesn’t broadcast
multiple runs for the same job.Fix styling glitches by adding aboot.csswhich is used as long the.lessfiles aren’t compiled yet.v1.2.4Fix run broadcaster so that it doesn’t send runs to the workers when there
is still an other run for the same job active (in queue or started).Fix autoselect environment settings.Update hostnames in configuration.v1.2.3Add filters to limit the number of displayed jobs.Add status icon to display if there is a connection with the WebSocket serverAdd option for monthly re-schedulingNote:monthly re-scheduling works
by incrementing thedtswith the number of days that are in thedts.
When incrementing by multiple months, it will check the days for each month.v1.2.2Add description fields to projects, workers, job-templates and jobsAddTransactionMiddlewareFix rescheduling when two runs are active of the same jobv1.2.1Add MySQL to requirements.txt (since the python setup.py install is
creating a zipped .egg which doesn’t work when the user does not have
a homedir (or when the homedir is not executable).v1.2.0Show job details in a column instead of a modalShow last 100 runs of a job incl. duration graphFixAUTHENTICATION_BACKENDSsetting for staging and production
(withoutModelBackendincluded, permissions are not working!)A job-title must now be unique per job-templateShow re-schedule interval in job detailsv1.1.1Fix dependencies insetup.py(was not using the development version
from GitHub).v1.1.0Run and job details are made deeplinkableRuns and jobs that are suspended are greyed-outv1.0.0Fix size (height) of run / job headersFix order of run objectsFix escaping of HTML characters in job script and log outputEnable timezone, all data is now presented (and expected to be) in theEurope/AmsterdamtimezoneOrder scheduled runs ascending (first to run on top)Add option to schedule children or not, when manually scheduling runsv0.7.4Internal related changes.v0.7.3Addjob_runner.settings.env.production_longrunsettings module for long
running processes to avoid “cached” results.v0.7.2Fix issue where filtering the groups would result in duplicated results.Remove WebKit browser notifications, since it was breaking the front-end in
Firefox.v0.7.1Check that runs received from the WebSocket server are within the current
active project.Add WebKit browser notifications.v0.7.0Major refactor:It is now possible to use AD assigned groups when
creating projects. Since basically all models are changed / renamed, it was
not possible to migrate old data to the new structure. Therefore you should
re-create the database!Addbroadcast_queuemanagement command to publish enqueueable runs to
the workers.v0.6.2Add missing static-file and logging settings.v0.6.1Add MySQL package as a requirement + update requirements in docs.Make it possible to override production settings.v0.6.0Create standalone application.Add overview of jobs + scheduling.