Continuous Build and Other DevOps Anti-Patterns and How to Overcome Them
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot DevOps anti-patterns and how to work your way back to a sane way of working. Continuous Build is an anti-pattern that Tom Stiehm has seen often, where a team will have what they call Continuous Integration (CI) in place, but it only builds the code. There are no unit tests or static analysis run. Certainly, this is better than not building, but it leaves a lot of health check information on the table that is considered part of CI. Without this information, you can never really gain the confidence that your build is healthy. The whole goal of CI is to feel that your build is healthy, so no tests and analysis means you aren’t doing CI. Just like CI, other DevOps practices can take time to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common DevOps anti-patterns and how to correct them.