Pre-Tested Commit: No broken code in your version control. Ever.
Typically, your team submits code to Version Control BEFORE verifying that it works, and risks breaking the build every single time — causing more problems than necessary. That's why TeamCity is different.
Unlike the standard scenario (edit, commit, verify), TeamCity's Pre-tested Commit feature allows you to remotely verify your changes BEFORE committing them to the VCS.
If your changes pass, TeamCity (in cooperation with your IDE) AUTOMATICALLY commits them to Version Control. If they fail, your code won't be submitted to the VCS and you'll receive a notification (by email, IM, your Windows System Tray, or in your IDE), allowing you to fix the failed code immediately. And unlike the standard scenario, you'll always know WHO broke the code. Most importantly, your team never stops working and there is never broken code in your Version Control.
And that's not the only big difference in TeamCity.
Other TeamCity features include:
- A Distributed Build Grid architecture — Your computer never slows down to run builds. You can simultaneously run builds for different Configurations (app servers, platforms, databases, frameworks, etc) — making Continuous Integration more continuous
- Remote Run — The same thing as Pre-tested Commit, on the Distributed Build Grid, without the Commit
- Server-side code analysis and code coverage — seen directly in your IDE (only for IntelliJ IDEA-based IDEs users for now)
- Tight IDE integration — allowing such things as jumping directly from an error report to the exact line in your IDE where the test failed — as well as many other features. TeamCity works closely with your favorite IDEs: IntelliJ IDEA-based IDEs, Eclipse, and Microsoft Visual Studio
- Rich web interface — with detailed and well-organized information. See for yourself in our Test Drive Center
Banish broken code from your version control. Forever.
Learn more about TeamCity's features.
Check out TeamCity in use on actual projects in our Test Drive Center.