Continuous integration on hosted platforms.
WHAT PIPELINES DO
Run defined steps automatically when changes occur.
WHAT TO RUN ON EVERY CHANGE
Build Formatting and linting Tests Security and dependency scanning
WHAT TO RUN ON MERGE TO MAIN
Those, plus building a deployable artefact.
WHAT TO RUN ON RELEASE
Deployment, with approval where appropriate.
WHAT TO ENFORCE
That checks pass before merging.
WHY
A check that can be bypassed is eventually bypassed.
WHAT TO KEEP FAST
The pipeline.
WHY
A slow pipeline is worked around, and feedback arrives too late to be useful.
WHAT TO DO ABOUT SLOWNESS
Cache dependencies Run independent jobs in parallel Run slow suites separately
WHAT TO STORE SECURELY
Credentials, as platform secrets, never in configuration files.
WHAT TO BE CAREFUL WITH
Pipelines triggered by outside contributions, which must not expose secrets Third-party actions or steps, which execute with your permissions
WHAT TO PIN
Versions of anything the pipeline uses.
