Hudson vs TeamCity: What are the differences?

# Introduction

1. **Integration with Git**: The key difference between Hudson and TeamCity is how they integrate with Git. TeamCity has better native support for Git compared to Hudson, offering more features like branch spec mapping, quiet period for triggers, and built-in pull request support.
2. **Built-in tools**: TeamCity comes with a variety of built-in tools and plugins that make it a more comprehensive solution out of the box compared to Hudson. These tools include code coverage, duplication finder, and integrated code inspections.
3. **Build Chains**: TeamCity offers a feature called build chains, which allows users to create more complex build workflows compared to Hudson. With build chains, users can define dependencies between different builds to ensure they are executed in the right order.
4. **User Interface**: TeamCity has a more modern and user-friendly interface compared to Hudson, making it easier for users to navigate and configure their builds. The user interface in TeamCity is also highly customizable, allowing users to tailor it to their specific needs.
5. **Remote Run**: TeamCity offers a unique feature called remote run, which allows developers to trigger a build on the CI server directly from their IDE. This can significantly improve the development workflow by enabling developers to quickly test their changes without leaving their development environment.
6. **Build Failure Conditions**: TeamCity provides more advanced build failure conditions compared to Hudson, allowing users to set up rules for when a build should be marked as failed. This can help teams maintain a higher quality codebase by catching issues early in the development process.

In Summary, Hudson and TeamCity differ in their integration with Git, built-in tools, build chains, user interface, remote run capabilities, and build failure conditions.