CONQUERING CONTINUOUS INTEGRATION & DEPLOYMENT

ABOUT MEAgency & Community Engineer

Instructor

Founder

REACH OUTAll the socials as

@tessak22

me@tessak22.com

tessakriesel.com

CONTINUOUS INTEGRATION

“ 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.

CONTINUOUS DELIVERY

CONTINUOUS DEPLOYMENT

AUTOMATE ALL THE THINGS

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

INVEST TIME IN AUTOMATION

KEEP YOUR SOFTWARE UP TO DATE

BUILD STEPS‣ Setup our containers ‣ Install dependencies ‣ Complete task runners ‣ Run automated tests ‣ Behat ‣ Coding Standards ‣ Visual Regression

‣ Deploy to staging or test

github.com/tessak22/conquering-ci

EXAMPLE BUILDThere is nothing more exciting then finally fixing your build.

SETUP CONTAINERS

INSTALL DEPENDENCIES

TASK RUNNERS

AUTOMATED TESTING

SERVER DEPLOYMENT

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!

FEEDBACKI would love to hear what you think!

tessakriesel.com/feedback

Anonymous feedback is a-okay, none of the form fields are required.