Conquering Continuous Integration & Deployment

Conquering Continuous Integration & Deployment

Continuous Integration is becoming an important part of the development process. However, to some, the how and why are still a bit fuzzy. This session talks about the natural progression of a development team and how each important piece of the development process can be automated via Continuous Integration & Deployment. I will also walk through an example WordPress project using Continuous Integration, Delivery & Deployment that implements Sass Compilation, Automated Testing & Deployment to a Server. Attend. Absorb. And you too can conquer.

3734ba5f47b3e579b367b4202aaba163?s=128

Tessa Kriesel

March 09, 2018
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 tessak22.com Please

    share pics and commentary using #mwphp18
  4. None
  5. INTEGRATION @tessak22

  6. CONTINUOUS @tessak22

  7. TEAM DYNAMICS @tessak22

  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 @tessak22

  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 @tessak22
  18. AUTOMATE ALL THE THINGS @tessak22

  19. TEAM TECHNOLOGIES Dev Contractors

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

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

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

  24. CONTINUOUS DEPLOYMENT @tessak22

  25. WHAT NOW? 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 one of the problem areas @tessak22
  26. FEEDBACK I would love to hear what you think! joind.in/talk/bfcfe

    @tessak22 Github Repo: bit.ly/tessa-ci