Baby Steps: Get Your DevOps Process Started By The End of This Session

Alternate title: "Okay, we've installed Jenkins. Now what?"

DevOps is in the sweet spot for many medium size development firms, but it can be a tougher fit for others. When management is used to doing things a certain way, they can perceive the barriers to entry and risks of "merging" the development and operations teams to be too great to justify the potential rewards. Smaller teams or firms might not want to invest the time to get a big Java-style build server configured, especially when they don't host production themselves.

But DevOps doesn't have to be all or nothing and doesn't need new squares on the Org Chart to see benefits. In this session, we will examine low-risk changes you can make to the way you do things now that will start you down the DevOps path:

  • Writing more testable code
  • Moving your unit and functional tests outside of Drupal
  • Using commit hooks
  • Getting your project managers involved
  • Integrating with a third party Operations Department

    You should be able to see at minimum the following benefits:

  • Better code coverage with automated tests (or at least better awareness of gaps of coverage)
  • Fewer bugs making it to staging, let alone production
  • Faster turnaround for feature requests

    If you see those benefits, you might decide to drink more of the DevOps Kool-Aid; if not, you at least know what you're missing.

  • Schedule info
    Status: 
    Proposed
    Session Info
    Speaker(s): 
    Track: 
    DevOps
    Experience level: 
    Beginner