Project challenges / verified progress
Beacon: ship it without fear

The engineering notebook

Make checks enforceable

How does the first GitLab pipeline prove Beacon still builds?

Loading Vault account...
Trust the path

Step 01 of 06

Understand the idea

Continuous integration (CI) runs checks on a clean machine when code changes. This helps catch problems that only seem to work on one developer’s computer.

ONE EVENT MANY JOBSpush or merge requestevent starts runvetstatic mistakesgo vettestrace detector on-racebuildbinary compileslinux amd64
A trigger fans out into independent jobs. Matrix builds are the same idea with variables: describe the job once, then evaluate it for each Go version.
Step 01

Key technical ideas

The runner starts clean

A hosted runner is created for a job and thrown away after it finishes. It does not have your aliases, uncommitted files or module cache unless you ask for one. This is why CI catches 'works on my machine' bugs.

Events decide when evidence is collected

merge_request_event checks proposed code before it enters the protected branch. push checks the branch after merge or direct update. You want both because they answer different questions about different repository states.

A cache key is a correctness claim

Caching Go modules saves time, but only when keyed by dependency files such as go.sum. A cache keyed only by operating system can restore stale packages and produce builds that are fast, green and wrong.

Required checks make advice enforceable

A green check is decoration until branch protection requires it. Required status checks force the merge button to respect the pipeline and make failures visible as blocked merges, not Slack folklore.

A tiny CI pipeline
# Show the latest pipelines for this project.
glab ci list --per-page 3

The shape is already complete: event, job, runner, checkout, toolchain, command. Beacon adds vetting, race detection, build output and branch protection.

Events and jobs carry different meaning

ThingExampleQuestion answered

Event

merge_request_event

Should this change enter?

Job

test

Does evidence pass?

Step

go test -race ./...

What produced it?

Runner

ubuntu-latest

Where did it run?

Matrix

Go versions

Does it hold twice?

Technical terms used at work

  • Pipeline configuration — The .gitlab-ci.yml file at the project root that defines stages, jobs, and when they run.

  • Runner — The machine that executes a job.

  • Matrix — A job expansion for several variable values.

  • Required pipeline — A protected-branch rule that blocks a merge until the pipeline passes.