In many organizations, releasing a new version of an application is an enormous undertaking: 1. Infrastructure needs to be in place 2. The code needs to be built (install dependencies, compile code, generate assets, etc.) 3. The code needs to be tested 4. The code needs to be configured 5. The code needs to be deployed The objective of this talk is to show you how to establish a process to merge and deploy code using best practices. In the process, we will define a system to continuously deploy a PHP application without breaking the bank.


Comments are closed.

Ian Guinn at 13:59 on 20 Sep 2018

great discussion about CI pipeline, we can definitely use this information.

Jesse D at 14:24 on 20 Sep 2018

covered a lot of ground, great examples

A lot of great information with good, practical examples.

As this is an introduction to CI/CD pipelines, it might make sense to tone down the "look at all of the scaling we can do" emphasis and instead focus on a smaller, single-server instance. It's great to know Elastic Beanstalk is able to handle four different deployment schemes, but it felt as though an inordinate amount of time was spent on that for a beginner-level, "why should we use CI/CD?"-type of talk.

Juan had a lot of great info on how to do CI/CD with Amazon products - I think if you're going to focus so heavily on one ecosystem, it should be in the title/description of the talk.

I'd suggest not trying to do the live PR and build part, and spend more time explaining some basics and "why" for the audience. Slides need to be way more readable, the font/size/color was very difficult to read.