Using Jenkins to Build Apache VHosts for GitHub Pull Requests on PHP Apps
summary
Automates per-PR test sites by checking out each GitHub pull request, creating /var/www/pr{N}/web, and wiring Apache via a mod_vhost_alias pattern plus a wildcard BIND zone so pr3.test, pr4.test, etc. resolve; Jenkins (1.5xx) uses the Jenkins GitHub Pull Request Builder plugin with a refspec and SHA-1 variable to build each PR, run tests, and post status back to GitHub. Demo shows multiple live PR sites (one returns forbidden if no index file). Warns that auto-building untrusted PRs is dangerous and lists Debian/Apache2.2/PHP5.4 as the tested stack.
AI-written summary · about
chapters (10)
- 0:00Introduction to project
- 1:04Professional background
- 3:49Development challenges
- 6:23The pull request solution
- 8:54Automated environment benefits
- 12:21System architecture setup
- 17:18Jenkins configuration
- 23:24Automating deployment
- 26:11Live demo and troubleshooting
- 41:16Conclusion and resources
related talks
44mUsing Jenkins to Build Apache VHosts for GitHub Pull Requests on PHP Apps
35mPractical PHP Deployment with Jenkins
38mWhat's Really to Blame?
45mHighway to Continuous Integration
29mJenkins + GitLab + RabbitMQ + Symfony2 + Phing
45mTesting PRs in a distributed PaaS environment
25mBuilding GitHub Actions in PHP with Minicli
44mSpreading the JAM throughout your CI workflow