Automation Cockpit 2.4 — parallel job runs and a rebuilt log viewer

The release turns the job runner from one-at-a-time into a scheduler, and replaces the log pane with a viewer that can hold a day's output without slowing down.

Until now a workspace ran one automation job at a time. That was fine when a job meant a build; it stopped being fine once people started chaining data jobs behind them. 2.4 runs jobs in parallel up to a limit you set per workspace, and shows the queue as a strip along the top of the runner so you can see what is waiting behind what.

The log viewer was rewritten around a virtual list. Earlier versions kept every line in the DOM and began to stutter somewhere past twenty thousand lines — which a long-running job reaches before lunch. The new viewer holds a million lines, filters as you type, and keeps the scroll position when a job writes to the tail.

Upgrading is in place. Workspaces, job definitions and saved filters carry over; the first start after upgrading re-indexes each open project, which takes a few seconds on a medium codebase.

In this release

• Parallel job execution with a per-workspace concurrency limit (default 4).
• Queue strip showing running, waiting and blocked jobs.
• Rewritten log viewer: virtualised, type-to-filter, stable tail-follow.
• Job definitions can now declare a dependency on another job by name.
• Fixed: the runner occasionally reported a cancelled job as failed.

The product

• Automation Cockpit — read the case