CI/CD is the New Lock-In

Welcome to 2022! Let’s start blogging this year on an impressive note, and point out that we’re in the process of creating the biggest lockout we’ve ever seen. And I mean always. Hardware locking in the old days where Seller A was incompatible with Seller B might have been worse, but at least the one we admitted when we signed the contract. This one is growing on us as I write.

Our DevOps environments can’t run in 2022 without what I like to call a “toolchain console”: GitLab, Github CI/CD, Atlassian, CircleCI, Jenkins – whatever you’re using. Just as you need some form of flow control or taps to run running water, you need a CI/CD environment to make DevOps work.

You are. Not possible. alive. without. He. She. And like any other vendor solution, CI/CD resellers will not be in a hurry to help you transition to a competitor. Switching won’t be easy or cheap, in large part because we’re transferring everything that might have been on a computer that had developed code running on it in the toolchain.

Sooner or later, we’ll fall back on the kitchen sink’s definition of “What is DevOps?” , but I expect that until then we will have to answer “…a lot of what we do”, because DevOps, by definition, is-to-end. It comes down to the process and all the steps from design to production.

No matter the length or complexity of the process by which an organization’s CI/CD tool is run, a plan must be in place to replace it. A viable plan, not a checkbox plan. When Atlassian decided it preferred cloud-based clients, it shocked its customer base. Atlassian was wise enough to leave an option to customers who really had to have an on-site solution, but it’s not hard to imagine them phasing out that option gradually, or to imagine another vendor dropping on-site support altogether. Some of the most competitive offerings in the industry — GitLab comes to mind — are already online-only, which makes this option even more attractive to other sellers because it’s now proven to be viable.

So, you have a plan. This is more important, IMO, than the cloud vendor lock. Cloud vendors are a small community, and they all understand each other, so if the push comes through, you can find help navigating the three big cloud vendors. There are dozens of DevOps console-type solutions in regular use, some of which are not at all CI/CD solutions (application version synchronization tools and software infrastructure management tools are areas that do CI/CD duty in some organizations, for example), so you won’t There is a lot of help navigating between them unless you can find a very specialized skill set to match the move you want.

So, you have a plan. Yes, I am already repeating myself. Know what you need to do before you do it. Include what to do if the main DevOps console crashes. Because it will, sooner or later.

And it kept swinging. Protect your artwork by protecting what builds it. And keep rolling out the tools your users need. It’s a new year – learn a new skill and use it to produce more cool things. I haven’t picked a new skill yet, but I’m taking the last tip myself. And again, in the New Year, I thank you for all those who do not know how to say it.

Leave a Comment