Skip to content
PREFLIGHT 0.9.0
Menu

What the components cannot force#

An included component is a set of ordinary jobs. The app's own .gitlab-ci.yml is merged over them, so an app can override a job's keys, skip it with rules, or delete the include: line. Preflight makes the safe pipeline the easy one; it does not lock it. Rollcall is where skipped or weakened gates will show up. A preflight checklist only works if the pilot reads it. This page lists which jobs may be allowed to fail and the five project settings that make the gates harder to skip.

Which jobs may be allowed to fail#

Four components take an allow_failure input, all defaulting to false: proctor, secret-detection, a11y and squire-kit. A policy finding is a warning while an app adopts PROCTOR's rules, a secret finding while a repo allowlists its first false positives, an accessibility finding while a site fixes what the gate found on its first run, and a kit finding while a repo puts its deploy kit back to Squire's files, so each job may fail without failing the pipeline during adoption; the first three still write their reports. composer-audit and npm-audit have no such input on purpose: a known advisory must fail the pipeline. The other jobs have no allow_failure input either.

No template adds a global key such as default:, variables:, workflow: or stages:. tests/check-contract.sh (and its .ps1 twin) fails on any top-level key in a template that is not a job named in contract/inputs.json, so a global key fails composer ci.

Protection checklist#

A pilot signs each line of the checklist; the plane does not sign for you. Five project settings make the gates harder to skip, and every one of them works on GitLab Community Edition: