DIY CONTINUOUS INTEGRATION
You know what Continuous Integration is. You have heard it mentioned at every conference and at every meetup. It’s part automated testing, part automated deployment, part test-driven development, part every other DevOps catch-phrase. Now you are ready to get started implementing CI practices. This session has three goals:
1.) explain what continuous integration means relative to web development, using Drupal as a test case.
2.) Introduce the tools available to implement CI now.
3.) Demonstrate what a CI implementation looks like in practice.
This session will explore what Continuous Integration is and is not with step by step examples and a DIY kit to get you exploring more. Continuous Integration touches all parties: clients, project managers, system admins, and developers, front and back end. If that’s you, you need to know what CI is.
Developer, Promet Source
Michelle Krejci discovered Drupal in graduate school when searching for a solution for managing the workflow of her department's academic journal. Excited by Drupal's potential to aid and enhance many of academia's processes and projects, Michelle decided that her first move after graduate school was to move from project owner to developer. Michelle has been working for Chicago's Promet Source since then, responsible for auditing new clients, initiating new clients into Drupal-speak, and tackling the more technical issues that arise from the Support Desk. Michelle has been passionate about advocating for incorporating continuous integration practices into Drupal development to heed off problems that arise in support before they start.