Simplified Continuous Integration with Laravel and Jenkins
summary
Builds a minimal CI pipeline that actually runs: a Jenkins master on a DigitalOcean droplet and a separate deploy server, GitHub SSH keys for Jenkins, branch-triggered jobs for staging, build steps like composer install; php artisan key:generate; phpunit and tarballing, then transfer via the Publish over SSH plugin into releases/current, atomic symlink swap, sudoers rules to restart nginx/php‑fpm and set permissions. The demo runs and shows console output so the flow completes end to end.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:05Why Bother with Continuous Development?
- 1:57Why Jenkins?
- 3:17Assumptions
- 3:32Why Digital Ocean?
- 4:11New Digital Ocean Droplet
- 4:50Accessing the New Server
- 5:21Setup ufw (firewall)
- 6:11Install Jenkins
- 7:06Access Jenkins
- 8:22Jenkins SSH Key
- 9:03SSH Key for Github
- 14:13Setup Your Deploy Server
- 16:20Add Deploy Server to Jenkins
- 18:36Create a New Project: General
- 18:55Create a New Project: Source Code Management
- 20:10Create a New Project: Build Options
- 22:44Create a New Project: Post Build Actions
- 26:55Build It
- 27:23What About Gitlab?
- 29:06What About Other Frameworks?
- 29:50What About Pipelines?
- 32:00Questions? Find me!
related talks
42mZero to Jenkins: Automatic builds + deploys
51mJenkins or: How I learned to stop worrying and love automation
35mPractical PHP Deployment with Jenkins- 35mPractical PHP Deployment with Jenkins
36mUsing Jenkins to Build, Deploy, and Automate Projects
40mThe Butler Did It: Putting Jenkins To Work For You
01h 00mContinuously delivering PHP projects
30mImplementing Continuous Deployment with Jenkins & Gerritt