DevOps Journey Part 2 – CI/CD

In our client’s DevOps journey, we are shooting for an efficient, stable, and reactive development-to-production workflow in your infrastructure. Let’s talk about the Continuous Improvement/Continuous Development (CI/CD) phase along the journey!

FAILURE IS AN OPTION!

It’s in your best interest to fail and FAIL FAST. What? No, that’s not a confused marketing strategy to simply get your attention. Okay, seriously, we really don’t want our clients to fail at anything. What you really want is to get features out the door. If that’s the case, it’s important to detect failures in your infrastructure as soon as they happen or to create processes that head off failure before it happens.

CI/CD means creating automated tools around the process of failure detection.

Last time, when we talked about “Works for me,” we identified some pain points associated with that theme. There is also pain that our approach to CI/CD can solve. Sometimes, when you roll out a new feature, it breaks an old feature which may never have been tested. The result is that it can take way too long to get features out the door. We can’t promise that stuff won’t break but, through processes of continuous improvement and development, we’re really good at quickly figuring out what’s broken, so your developers can save time and you can roll features out much faster.