Jenkins + GitLab + RabbitMQ + Symfony2 + Phing
summary
Jenkins + GitLab automatically builds any merge request and rebuilt on merge acceptance, using the Merge Request and Build Now plugins; Phing runs the actual steps—composer, bower, linting, tests, cache clear—via the Phing plugin. A post-build bash task publishes a RabbitMQ message to a topic exchange; a Symfony2 consumer receives it, checks out the built commit, runs Phing deploy targets to install and roll back on failure. All services live on DigitalOcean; multi-server fanout is planned but currently only the dev single-server flow is working and so far has not failed.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:37About Me
- 4:05Why Jenkins?
- 6:58Why GitLab? Why Not GitHub or BitBucket?
- 9:28Jenkins + GitLab Workflow
- 13:59PHP Code Sniffer
- 14:42Build Summary
- 15:45What About Deployment?
- 18:04A brief explanation of how RabbitMQ works
- 18:56Types of exchanges
- 19:53Message Example
- 24:24Bringing It All Together
- 25:04All The Jenkins Things
- 25:32Things I Feel Are missing
related talks
33mSimplified Continuous Integration with Laravel and Jenkins
43mCI⚡CD: theory put into practice
40mThe Butler Did It: Putting Jenkins To Work For You
42mZero to Jenkins: Automatic builds + deploys
38mWhat's Really to Blame?
38mDeploying your apps... the right way!
01h 00mContinuously delivering PHP projects
35mPractical PHP Deployment with Jenkins