Overview

TeamCity

Stacks1.2K

Followers1.1K

Votes316

Buildbot

Stacks73

Followers128

Votes27

GitHub Stars5.4K

Forks1.7K

Buildbot vs TeamCity: What are the differences?

Architecture: Buildbot is a distributed system that runs on a master-slave architecture, where the master coordinates multiple slaves to execute build jobs. In contrast, TeamCity employs a server-agent architecture where the central server manages agents that execute build tasks independently.
Flexibility: Buildbot provides more flexibility in configuration as it allows users to script their build processes using Python. On the other hand, TeamCity offers a point-and-click interface for configuration, making it easier for users without scripting knowledge to set up builds.
Integration: TeamCity has seamless integration with popular version control systems like Git, Subversion, and Mercurial, making it easier to set up build triggers and monitor code changes. Buildbot, although it supports various VCS tools, might require more manual configuration for smooth integration.
Community Support: Buildbot is an open-source project with a vibrant community that actively contributes to its development and provides support through forums and documentation. TeamCity, being a proprietary tool developed by JetBrains, offers professional support services but may lack the same level of community-driven resources.
Customization: Buildbot allows extensive customization of the build pipeline and notification systems to fit specific project requirements. In contrast, TeamCity offers a more user-friendly interface for customizations but may have limitations in certain advanced customization scenarios.
Licensing: Buildbot is released under the MIT license, making it free for commercial use and modification without restrictions. TeamCity, being a commercial product, requires a paid license for full access to all features and support services.

In Summary, Buildbot and TeamCity differ in architecture, flexibility, integration capabilities, community support, customization options, and licensing terms.

🔥 Trending in Continuous Integration on StackShare

GitHub Actions Continuous Integration

Automate your workflow from idea to production

Try it View Docs Alternatives

Try

4.23k

3.11k

Advice on TeamCity, Buildbot

Sri Srinivas

Feb 11, 2020

Needs advice

I want to start automatic regressions for nightly builds and also continuous integration builds. The tests I ran are part of my regression suite. And I want to track the results of these tests.

I am able to do this with Jenkins using the Junit plugin. But, I am trying to do the same with Buildbot, and I am not able to get the report of the tests. So, I just want to know is it possible to get the reporting of tests through Buildbot. If yes, could anyone provide some examples

121k views121k

Comments

Detailed Comparison

TeamCity	Buildbot
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.	BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure.
Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface; Simplified setup: create projects from just a VCS repository URL;Run multiple builds and tests under different configurations and platforms simultaneously; Make sure your team sustains an uninterrupted workflow with the help of Pretested commits and Personal builds; Have build history insight with customizable statistics on build duration, success rate, code quality, and custom metrics; Enable cost-effective on-demand build infrastructure scaling thanks to tight integration with Amazon EC2; Easily extend TeamCity functionality and add new integrations using Java API; Great visual project representation. Track any changes made by any user in the system, filter projects and choose style of visual change status representation;	run builds on a variety of slave platforms;arbitrary build process: handles projects using C, Python, whatever;minimal host requirements: Python and Twisted;slaves can be behind a firewall if they can still do checkout;status delivery through web page, email, IRC, other protocols;track builds in progress, provide estimated completion time;flexible configuration by subclassing generic build process classes;debug tools to force a new build, submit fake Changes, query slave status;released under the GPL
Statistics
GitHub Stars -	GitHub Stars 5.4K
GitHub Forks -	GitHub Forks 1.7K
Stacks 1.2K	Stacks 73
Followers 1.1K	Followers 128
Votes 316	Votes 27
Pros & Cons
Pros 61 Easy to configure 37 Reliable and high-quality 32 User friendly 32 Github integration 32 On premise Cons 3 High costs for more than three build agents 2 Proprietary 2 User-friendly 2 User friendly	Pros 9 Highly configurable builds 5 Hosted internally 5 Beautiful waterfall 4 Free open source 3 Python
Integrations
Slack	No integrations available

What are some alternatives to TeamCity, Buildbot?

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.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.