The CI tab, how to read it
Every push gets checked by the build server before it can ship. The CI tab in the bottom panel shows that work live, so "why is my deploy not out yet" has an answer on screen instead of a guess. Open it from More and drag it into the row if you want it always at hand. It refreshes itself every five seconds while you look at it and stops when you look away.
The tab reads the build server through the LogiShell node it runs on. If none of your connected machines runs it, the tab says so in one sentence.
Read it top to bottom
Delivery. Four steps from left to right: dev, staging, main and
prod. Each shows the commit it is on and what the checks said about that
commit:
- checks passed: the commit is green and may move on;
- checks failed: something is red, look at the runs below;
- being checked: a run for this commit is going right now;
- not checked yet: no run has answered for this commit.
prod is the commit the web app serves right now. When it differs from
main, a line under the strip says so: the newest work is not live yet.
Queue. Runs waiting for a free machine, first in line on top. Each line says which task or branch it is, which kind of machine it needs (heavy for full builds, light for quick checks), how long it has been waiting, and what started it. A long queue behind one heavy machine is the usual reason a deploy waits.
Machines. The computers that run CI jobs. A green dot is online and idle, an accent dot is online and busy (the line names the job, the branch and how long it runs), a grey dot is offline with the time it was last seen. Machines silent for a day or more are folded away at the bottom.
Running and recent. Runs that go now, then the ones that finished in the last two hours, newest first. Each small square is one job: green passed, red failed, accent running, amber waiting, grey skipped or cancelled. Click a run to see its jobs with their times.
When a job fails
The tab does not dump the log on you. A failed job gets one sentence:
- "ts" failed after 10m. Open the log to see the first error. The link opens that job's log on the build server.
- never reached a machine: nothing ran. The machine lost the job on the way. There is nothing to fix in the code; run it again.
- was stopped before it finished. A newer push to the same branch usually replaces the older run.
What it does not do yet
The tab only shows. Cancelling, re-running and moving a run up the queue come in a later version; until then those stay with the people who run the build server.