This article was brought to you by Adeyinka Adegbenro, draft.dev. Developers know the frustration well. Code works perfectly on their laptop, then breaks the moment it hits staging or production. I

JetBrains is a software development company known for its suite of developer tools, including integrated development environments (IDEs) such as IntelliJ IDEA, PyCharm, and WebStorm. Through its platform, JetBrains provides developers with powerful tools for coding, debugging, and collaboration, across a wide range of programming languages and frameworks. From their blog developers can learn about JetBrains' IDE features, productivity tips, and best practices for using its tools effectively to streamline their development workflows and boost productivity.

JetBrains

TeamCity's pretested commits feature validates code changes on CI servers before they reach the main branch, preventing broken builds from disrupting team workflows. The workflow reverses the traditional commit-then-build process: developers push changes to validation branches (like remote-run/* in Git), TeamCity runs full build and test cycles, and only passing code gets merged. This approach catches environment-specific issues early, maintains stable main branches, and reduces time wasted debugging others' broken commits. The feature works differently for distributed systems (Git uses branch remote runs) versus centralized VCS (SVN/Perforce use IDE patches). Best suited for teams prioritizing stability with solid automated tests, though effectiveness depends entirely on test suite quality.

Say Goodbye to "It Works on My Machine": A Look at TeamCity's Pretested Commits

The problem: Broken builds from unverified commits