Continuous Integration & Delivery @ Ohio Laravel

My local Laravel usergroup, Ohio Laravel, is a monthly opportunity to talk tech with some of the brightest PHP developers in Columbus.

At a recent meeting, somebody boasted how easy it is to “just zip up a PHP application and drop it on a server.”

“Better yet, SSH into the server, do a git pull , then run composer install!”, someone else chimed in.

As the resident testing advocate and pipeline geek, I was quick to chime in: “wait, what? Are you really still doing an SSH + git pull combo in 2019?”.

Long story short, I’ve been invited to talk about Continuous Integration and Delivery at the November Ohio Laravel meetup.

Build and Release Confidently with Continuous Integration and Delivery

Continuous Integration (CI) and Continuous Delivery (CD) are the Holy Grail for software development teams: no matter who pushes the feature, the same tests are run, the same processes are followed, and nothing gets released without satisfying well-defined quality standards.

Unfortunately, setting up that initial CI/CD workflow can be a bit daunting for teams that don’t have an experienced DevOps engineer.

Fear not, my dear developers! This talk breaks down the basic concepts of continuous integration, continuous delivery, and how to integrate them into your team’s workflow. Whether you’re working on a small side project or your next big idea, CI and CD can make the journey better.

For this talk, we’ll be using GitLab’s (free) CI/CD pipelines, but the principles translate well to any major CI/CD platform!

If you’re looking how to move your team from “SSH + git pull” to a proper, CI/CD pipeline, please join us November 6 at Ohio Laravel!