CI/CD pipeline

Works like GitHub Actions, GitLab CI or Jenkins. Get a made-up team's pipeline release-ready: fix tests that start before install, pull a printed secret and a pasted token out, test both supported versions with a lockfile cache key, gate deploys to main with a reviewer, and require the tests on main.

Release week at Fernway Labs, and the pipeline is yours to fix. (A made-up team and repository. Start with the brief.)

QuickCruit CI

fernway-labs/truck-ordersPrivate

All workflows

Every push and pull request runs .pipelines/release.yml. Commit the workflow to start a new one.

3 workflow runs

release.yml#558:Commit 5c41a07 pushed by nadia-valdiviamainFeb 162m 7s
release.yml#557:Pull request #164 by mateo-blackwoodfix/cart-roundingFeb 152m 7s
release.yml#556:Commit 7731eca pushed by hana-navarrofeature/waitlistFeb 142m 7s

main

Latest run #558

Release week on truck-ordersHana Navarro, head of engineering

v1.8.0 is cut for Friday and CI can't gate it yet. The unit-tests job has been red on main all week and nothing waits on it, so #164 got deployed to production straight from its PR, failing tests and all. Need the pipeline release-ready before we tag. Supported runtimes are whatever the README says, not what the workflow runs today.

Run #558 on main failed in unit-tests. Read the log and fix the cause in the workflow. Leave the tests alone.
bundle prints PARTNER_API_TOKEN to the log, and someone pasted the deploy token into release. Secrets live in the store, never in the file or the log.
Test on both Node versions the README supports, and make the dependency cache follow package-lock.json, so a bump never restores old packages.
Deploy only on a push to main, only after the tests pass, through the production environment. Nadia Valdivia signs off on every production deploy. A pull request never deploys.
Pull request #164 fails its tests and could still merge. Make unit-tests a required status check on main.

When you check, I play your committed workflow on a push to a feature branch, a failing and a passing pull request, a push to main, a dependency bump and a failing test on main.

Fernway Labs, the repository, the people and every token here are made up. A practice case, built for you.

Your list

Fix why unit-tests failsTo do
Keep secrets out of the file and the logsTo do
Test both versions, cache by lockfileTo do
Deploy from main only, with sign-offTo do
Require unit-tests on mainTo do

Commit your fixes, then check. I read what's committed and saved, not drafts.