BEbencherdev
runners

Persistent WebSocket channel for runner lifecycle

Changed on

➕ Bencher Plus: Single persistent WebSocket connection for job assignment and execution. Runner sends Ready to request a job, server pushes Job or NoJob. A runner that sends Paused instead gets NoJob at the end of its poll and no job. During execution, handles Running, Heartbeat, Completed, Failed, and Canceled messages. Authentication is via runner key in the Authorization header.

get/v0/runners/{runner}/channel

Request

  • The document declares no server URL.
  • Auth
    none declared

Path parameters

runnerstring required

The slug or UUID for a runner.

Changes