jobs

Data source: JuliaCI/julia-ci-timing

name

the Buildkite step name, with emoji codes such as :linux:

retry

attempt number within the build for that name, 0 first

state

passed, failed, canceled, broken, timed_out, ...

soft_failed

1 when the job was allowed to fail

duration_s

finished minus started, seconds

runnable_at

when the job could start; runnable to started is its queue wait

agent_hostname

the machine the job ran on

234,522 rows

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: queue, exit_status, soft_failed, created_at (date), scheduled_at (date), runnable_at (date), started_at (date), finished_at (date)

Next page

CREATE TABLE jobs (
    id                   INTEGER PRIMARY KEY,
    build_id             INTEGER NOT NULL REFERENCES builds (id),
    name                 TEXT NOT NULL,
    retry                INTEGER NOT NULL DEFAULT 0, 
    job_uuid             TEXT UNIQUE,                
    step_key             TEXT,
    kind_id              INTEGER REFERENCES job_kinds (id),
    agent_hostname       TEXT NOT NULL DEFAULT '',
    agent_name           TEXT,
    queue                TEXT,
    state                TEXT NOT NULL,
    exit_status          INTEGER,
    soft_failed          INTEGER,
    retried              INTEGER,
    retries_count        INTEGER,
    retry_type           TEXT,
    parallel_group_index INTEGER,
    duration_s           REAL NOT NULL,              
    created_at           TEXT,
    scheduled_at         TEXT,
    runnable_at          TEXT,
    started_at           TEXT,
    finished_at          TEXT,
    web_url              TEXT,
    change_seq           INTEGER NOT NULL,
    UNIQUE (build_id, name, retry)
);
CREATE INDEX jobs_name ON jobs (name, build_id);
CREATE INDEX jobs_seq ON jobs (change_seq);