WordCamp US: Conquering Continuous Integration and Deployment

3734ba5f47b3e579b367b4202aaba163?s=47 Tessa Kriesel
December 02, 2017

WordCamp US: Conquering Continuous Integration and Deployment

You know that Continuous something-or-other exists. Maybe you have even heard the terms Continuous Integration or Continuous Deployment, but not much more than that. I was in your shoes just a few short months ago. I came, I coded, I conquered. Now I am breaking it all down so you too can feel confident with the basics of continuous integration and deployment.

I will cover the basics of how to setup Github and Circle CI with WordPress and configure deployment to a staging environment. We will cover continuous-jargon and break down yml and script files to better understand how it works and how you can start to use it with your projects.

Attend. Absorb. And you too can conquer.

3734ba5f47b3e579b367b4202aaba163?s=128

Tessa Kriesel

December 02, 2017
Tweet

Transcript

  1. CONQUERING CONTINUOUS INTEGRATION & DEPLOYMENT

  2. ABOUT ME Agency & Community Engineer 
 Instructor Founder 2018

    Lead Organizer
  3. REACH OUT All the socials as @tessak22
 me@tessak22.com tessakriesel.com Find

    me on Twitter for my slide deck :)
  4. None
  5. INTEGRATION

  6. CONTINUOUS

  7. TEAM DYNAMICS

  8. TEAM TECHNOLOGIES

  9. TEAM TECHNOLOGIES

  10. TEAM TECHNOLOGIES

  11. TEAM TECHNOLOGIES

  12. TEAM TECHNOLOGIES

  13. TEAM TECHNOLOGIES Dev Contractors

  14. TEAM TECHNOLOGIES Dev Contractors

  15. “There is no single continuous integration and continuous delivery that

    will work for everyone. You are essentially trying to automate your company’s culture using bash scripts. - Kelsey Hightower
  16. CONTINUOUS INTEGRATION

  17. DAILY TASKS ‣ Write some code ‣ Compile some Sass

    ‣ Minify some Javascript ‣ Complete code reviews ‣ Internal testing or quality assurance (QA) ‣ Deploy to staging servers ‣ Communicate with your team ‣ Following procedures
  18. TEAM TECHNOLOGIES Dev Contractors

  19. AUTOMATE ALL THE THINGS

  20. TEAM TECHNOLOGIES Dev Contractors

  21. The master has failed more times than the beginner has

    even tried.
  22. BUILD STEPS ‣ Setup our containers ‣ Install dependencies ‣

    Complete task runners ‣ Run automated tests ‣ Behat ‣ Coding Standards ‣ Visual Regression ‣ Deploy to staging or test
  23. None
  24. CONTINUOUS DELIVERY

  25. CONTINUOUS DEPLOYMENT

  26. WHAT NOW? 1. Write down the steps to create a

    new project 2. Highlight any problem areas 3. Automate at least one of these steps 4. Automate at least one of the problem areas
  27. FEEDBACK I would love to hear what you think! speakerrate.com/talks/

    74061 Github Repo: bit.ly/tessa-ci