Need advice about which tool to choose?Ask the StackShare community!
Add tool
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.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Hudson
Pros of TeamCity
Pros of Hudson
Be the first to leave a pro
Pros of TeamCity
- Easy to configure61
- Reliable and high-quality37
- User friendly32
- On premise32
- Github integration32
- Great UI18
- Smart16
- Free for open source12
- Can run jobs in parallel12
- Crossplatform8
- Chain dependencies5
- Fully-functional out of the box5
- Great support by jetbrains4
- REST API4
- Projects hierarchy4
- 100+ plugins4
- Personal notifications3
- Free for small teams3
- Build templates3
- Per-project permissions3
- Upload build artifacts2
- Smart build failure analysis and tracking2
- Ide plugins2
- GitLab integration2
- Artifact dependencies2
- Official reliable support2
- Build progress messages promoting from running process2
- Repository-stored, full settings dsl with ide support1
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- High-Availability0
- Hosted internally0
Sign up to add or upvote prosMake informed product decisions
Cons of Hudson
Cons of TeamCity
Cons of Hudson
Be the first to leave a con
Cons of TeamCity
- High costs for more than three build agents3
- Proprietary2
- User-friendly2
- User friendly2
Sign up to add or upvote consMake informed product decisions
What is Hudson?
It monitors the execution of repeated jobs, such as building a software project or jobs run by cron. Among those things, currently it focuses on the two jobs
What is TeamCity?
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Need advice about which tool to choose?Ask the StackShare community!
Jobs that mention Hudson and TeamCity as a desired skillset
What companies use Hudson?
What companies use TeamCity?
What companies use Hudson?
What companies use TeamCity?
See which teams inside your own company are using Hudson or TeamCity.
Sign up for StackShare EnterpriseLearn MoreSign up to get full access to all the companiesMake informed product decisions
What tools integrate with Hudson?
What tools integrate with TeamCity?
What tools integrate with Hudson?
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+22 13
8704
+46 27
32615
+35 41
19056
What are some alternatives to Hudson and TeamCity?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Travis CI
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
GitHub Actions
It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.