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.

Transcript

1. CONQUERING CONTINUOUS INTEGRATION & DEPLOYMENT
2. ABOUT ME Agency & Community Engineer 
 Instructor Founder
3. REACH OUT All the socials as @tessak22
 me@tessak22.com tessakriesel.com
6. CONTINUOUS INTEGRATION
7. “Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. By integrating regularly, you can detect errors quickly, and locate them more easily.
8. CONTINUOUS DELIVERY
9. CONTINUOUS DEPLOYMENT
10. AUTOMATE ALL THE THINGS
11. DAILY TASKS ‣ Write some code ‣ Compile some Sass ‣ Minify some Javascript ‣ Complete code reviews ‣ Do internal tests or reviews ‣ Deploy to staging servers ‣ Do some more testing ‣ Deploy to production servers ‣ Communicate with your team
13. INVEST TIME IN AUTOMATION
14. KEEP YOUR SOFTWARE UP TO DATE
15. BUILD STEPS ‣ Setup our containers ‣ Install dependencies ‣ Complete task runners ‣ Run automated tests ‣ Behat ‣ Coding Standards ‣ Visual Regression ‣ Deploy to staging or test
16. github.com/tessak22/conquering-ci
17. EXAMPLE BUILD There is nothing more exciting then finally fixing your build.
18. SETUP CONTAINERS
19. INSTALL DEPENDENCIES
20. TASK RUNNERS
21. AUTOMATED TESTING
22. SERVER DEPLOYMENT
23. SETUP STEPS ‣ Fork or download repo in Github ‣ Create a free Pantheon site ‣ Create free CircleCI account ‣ Build Github project ‣ Edit project settings ‣ Add environment variables ‣ Add SSH key ‣ Rebuild project ‣ Start writing new code!
24. FEEDBACK I would love to hear what you think! tessakriesel.com/feedback Anonymous feedback is a- okay, none of the form fields are required.