Minimum Viable PHPipeline
summary
A concrete plan for PHP projects: set up Composer, run PHPUnit tests, enforce coding style with PHPCS/PHPCBF, and add static analysis with PHPStan using a baseline. Start with a minimum viable pipeline (checkout, install, phpunit, phpstan, phpcs), expand with a build matrix to cover PHP versions and extensions (his example generates ~350 jobs and can take ~20 minutes), add secrets for integration tests, artifacts, review deployments, mutation tests, memory‑leak checks and CDK → CloudFormation diffs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:46Talk relevance
- 3:52Continuous integration
- 7:08Composer and PHPUnit
- 10:23Testing habits
- 11:52Coding standards
- 13:16Static analysis tools
- 18:58CI pipelines in shell
- 21:47Minimum viable CI
- 23:10Code reviews in CI
- 28:29Build matrices
- 30:34Secrets in pipelines
- 33:01Common checks
- 37:59Deployment automation
- 40:28Shipping confidence
- 41:33Q&A
related talks
35mPractical PHP Deployment with Jenkins
35mPractical PHP Deployment with Jenkins
34mContinuous Integration
01h 00mContinuously delivering PHP projects
47mGitLab and PHP? It Works! Tips, Tricks and Learnings
33mSimplified Continuous Integration with Laravel and Jenkins
40mCode, Test, Deploy, Repeat
37mCI/CD for Laravel Applications: Automate, Optimize and Scale
