Midwest PHP 2018 Header

Tessa went over why you need continuous integration & deployment and very basically how to do it. The basic take away is that when you have a larger team having automated tests and deployment can save a lot of work

Main Take Aways

How to get started with CD & CI

  1. Write down the steps to create a new project
  2. Highlight any problem areas
  3. Automate at least one item from step 1
  4. Automate at least on of the problem areas

Things I’m Going to Do

I actually didn’t get much from this session because I’ve already setup a basic continuous integration & deployment process to the point where it’s a single step test and deploy.

My Raw Notes

  • Important in team dynamics
  • With one person you can use FTP for Deployment
  • With two people you need GitHub
  • With three people you need to add Sass and Gulp
  • With four people you need to add Wordpress for communication
  • With five you need to add slack
  • With more you need to start doing QA

“There is no single continuous integration and continuous delivery that will work for everyone. You are essentially trying to automate your company’s culter using bash script” - Kelsy Hightower

Continue Integration -> Dev practice that encourages developers to push into shared space several times a day.

Example Build Steps

  • Setup our containers
  • Install dependencies
  • Complete task runners
  • Run automated tests
    • behat
    • Coding standards
    • Visual Regressions

  • Deploy to staging or test

  • Continuous delivery - continuously delivering code every day
  • Continuous deployment - constantly deploying

How to get started with CD & CI

  1. Write down the steps to create a new project
  2. Highlight any problem areas
  3. Automate at least one item from step 1
  4. Automate at least on of the problem areas