Your CI Pipeline Validates Three Languages While Your Codebase Uses Eleven

Last Tuesday, a Terraform module made it through CI, passed code review, merged to main, and immediately broke three environments because someone had used deprecated syntax from version 0.12. The CI system never ran terraform validate . Why? Because the platform doesn't have a Terraform runner preconfigured, and nobody had 90 minutes to figure out how to add one. Meanwhile, your team runs eleven different language stacks in production. Your CI platform supports three of them out of the box. This is the polyglot infrastructure tax: the gap between "supported languages" and "languages we actually use." Every modern infrastructure team hits it. You're running Rust for performance-critical data pipelines, Go for Kubernetes operators, Python for ML serving, TypeScript for internal tools, and Terraform/Pulumi/CDK for infrastructure. Your CI platform pretends six of those don't exist. The Problem: Language Coverage Is a False Metric When you evaluate CI platforms, they tout "first-class suppo