ci-cd - JokerTech

Subscribe

ci-cd

A collection of 6 posts

PHPUnit, Psalm, PHP-CS-Fixer, ESLint: One CI Pipeline for a Small App

Photo Sweep has no runtime dependencies and a small codebase, and still runs a full static analysis, coding standard, unit test and lint stack on every push. The two worst bugs it ever had needed a real server, not more lint — which is the point, not the counterargument.

The Paperwork Nobody Tells You About Before Publishing a Nextcloud App

A signing certificate for the Nextcloud app store isn't self-service: you submit a CSR as a GitHub pull request and wait for a maintainer to sign it, days rather than minutes, and the CN has to exactly match your immutable app id.

The Signing Key Lifecycle: Generate, Back Up, Never Commit, Wire Into CI

Losing an Android release signing key means every future update is permanently impossible. Here is the full lifecycle: generate once, back up twice in different failure domains, and wire four secrets into GitHub Actions with an unsigned fallback for forks.

End-to-End Tests Across Chrome, Firefox, and Mobile Chrome for a Side Project

165 Playwright specs covering public pages, auth, dashboard, and admin — but CI only runs the Chromium project, and that tradeoff is deliberate, not an oversight.

A GitHub Action That Checks Your Own Deploy After It Ships

post-merge-prod-check.yml runs a small Playwright script against the real fishing.nissaar.com URL after every push to main — because a green CI build says nothing about whether the deploy actually worked.

What a Year of CodeQL Alerts Looks Like on a Solo Project

Eight code-scanning alerts, four distinct classes, fixed one at a time across a year of commits — the real pattern is that rate limiting had to be fixed six separate times before it stuck.