Using Jenkins to Build Apache VHosts for GitHub Pull Requests on PHP Apps
summary
Uses Jenkins + github pull request builder to check out each PR commit (refspec + SHA1), create /var/www/pr-tester/prN/web, and configure Apache with mod_vhost_alias plus BIND9 wildcard DNS so each pull request gets a live PHP site. Demo builds three PRs (pr3, pr4, pr5), serves pr3 and pr4 successfully, and returns Forbidden for pr5 because it only contains README.md. Notes concrete pitfalls: Jenkins must trust enterprise SSL certs in Java and avoid running multiple competing PR jobs for the same repo.
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
36mUsing Jenkins to Build, Deploy, and Automate Projects
42mZero to Jenkins: Automatic builds + deploys
51mJenkins or: How I learned to stop worrying and love automation
36mCI Monkey
33mSimplified Continuous Integration with Laravel and Jenkins
35mPractical PHP Deployment with Jenkins
40mThe Butler Did It: Putting Jenkins To Work For You
