feat(pipeline): standalone Blender renders on the same queue
Deploy / deploy (push) Successful in 7m2s
Deploy / deploy (push) Successful in 7m2s
Blender work is not a shot submission: no Export, no version, no validation, QC or delivery. It is "Ctrl+F12, but on the farm", so it is modelled as what it is — a queue entry and nothing more. That turned out to need very little. Claim, progress, fail and complete-render already tolerated a job with no Export behind them, so a Blender job reuses the whole lifecycle; RenderJob gains projectId, label and submittedBy so a job with no shot code still has something to show. Capability gating is new and was already missing: the claim now filters job types by the machine's reported tools. Without it a workstation without Blender would claim Blender work and fail it repeatedly, burning the attempts while a machine that could have rendered it sat idle. The worker asks for Blender jobs unconditionally and the server refuses them — trusting the worker to self-select would have left the same hole. The runner treats a clean exit with no saved frames as a failure: Blender exits 0 when a frame range is empty or an output path is unwritable, and a job that silently rendered nothing is the worst outcome available. Standalone jobs auto-requeue on a transient failure like any other work; delivery builds are deliberately excluded, since a half-written package wants a human first. Adds the Blender add-on (BlenderPanel/) and its docs. The add-on refuses to submit an unsaved file — the farm opens the .blend from disk, so unsaved changes would render the previous state without warning. Its payload is pinned by a contract test, since add-on and server only ever meet over JSON. Worker 1.5.0. Adds migration 20260815000000_blender_render_jobs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -59,6 +59,19 @@ export function isInWindow(windows: AvailabilityWindow[], now: Date): boolean {
|
||||
|
||||
export type ClaimGate = "normal" | "urgent-only" | "none";
|
||||
|
||||
/**
|
||||
* Job types a machine is equipped for. Capabilities are reported at
|
||||
* registration; a machine without Blender installed must never be handed a
|
||||
* Blender job, or it claims work it can only fail — repeatedly, until the
|
||||
* attempts run out — while a machine that could have rendered it sits idle.
|
||||
*/
|
||||
export function machineSupportedTypes(machine: { capabilities: unknown }, requested: string[]): string[] {
|
||||
const tools = ((machine.capabilities as { tools?: Record<string, unknown> } | null)?.tools ?? {}) as Record<string, unknown>;
|
||||
const hasBlender = Boolean(tools.blender);
|
||||
|
||||
return requested.filter((type) => (type === "BLENDER_RENDER" ? hasBlender : true));
|
||||
}
|
||||
|
||||
export function machineCanClaim(machine: Machine, now: Date): ClaimGate {
|
||||
if (!machine.enabled) return "none";
|
||||
if (machine.renderNowUntil && machine.renderNowUntil > now) return "normal";
|
||||
|
||||
Reference in New Issue
Block a user