Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Can you spot the configuration difference?

DZone's Guide to

Can you spot the configuration difference?

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.

One of our Dev (DevOps?) guys came across this inconsistency that broke a server, and said in scrum “without Metafor this totally would have taken me 5 hours to identify”. We got discussing various little slip of the pinky errors that can completely break a server. You know, extra/missing/wrong character in the config: nameserver, port, whatever. Or maybe your pinky slipped and suddenly your sources list has you grabbing from the wrong repo.

These types of config bugs can be a massive pain to identify. Looking through the config code line by line is bad enough, but a double key tap when you meant a single can create a mess our eyes generally suck at picking out – the ol’ golden needle in a haystack situation.

Oh, they call you “eagle eyes” around the office do they? I thought you might enjoy a little game of spot the difference :)

configuration difference

Hmmmmmmm, the times are different, that’s suspicious…

content difference

Now just imagine what a pain it would have been to pick out that bug if we didn’t find it and highlight it in yellow for you. To receive your diff report like the one above, join the Metafor Beta.

Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}