As a developer at Cloud Application Manager, I wear the IT Ops hat just as often as I spend time writing code. So I understand all too well the pain IT Ops endure to keep things running smoothly after a production update. In the continuous delivery world of devops where small, incremental code changes are deployed every day, chances are that IT Ops have to constantly put out fires. Luckily, in my own job, I’ve been able to leverage a combo of tools and workflows to catch the problems right where they originate — in the development environment.
Defining Reusable Components for the Development Stack
I believe that a developer’s dream should not turn into a nightmare for IT Ops. So I rely on a set of workflow and tools that help IT Ops like me sleep better at night. One such method is to provide a base level environment for the development stack. This stack usually comprises a company-approved base level runtime that is tested and production certified. The idea is that when it’s time to push updates in staging or production, the code is more stable and less likely to involve bugs or errors.
Let me give a simple example. At...