GitHub vs TeamCity

Overview

GitHub

Stacks295.6K

Followers259.0K

Votes10.4K

TeamCity

Stacks1.2K

Followers1.1K

Votes316

GitHub vs TeamCity: What are the differences?

Introduction

GitHub and TeamCity are both popular platforms used in software development. While GitHub is primarily a source code management and version control system, TeamCity is a continuous integration and deployment server. Although they have similar goals, there are key differences between GitHub and TeamCity that set them apart.

Hosting and Collaboration Features: One major difference between GitHub and TeamCity is their focus on hosting and collaboration. GitHub provides a complete platform for hosting and managing repositories, allowing developers to conveniently collaborate and contribute to projects. On the other hand, TeamCity, while offering some limited code hosting capabilities, primarily focuses on continuous integration and deployment workflows.
Integration and Build Automation: TeamCity is specifically designed to facilitate the process of building, testing, and deploying software. It offers comprehensive build automation features, allowing developers to run builds on different platforms, control dependencies, and manage complex build workflows. GitHub, while providing some basic build features, does not have the extensive automation capabilities of TeamCity.
Version Control and Code Review: GitHub is renowned for its powerful version control system, Git. It offers advanced branching and merging capabilities, making it easier for developers to manage parallel development efforts. Additionally, GitHub provides built-in code review features, allowing teams to collaborate and provide feedback on code changes. In contrast, TeamCity focuses more on the build and deployment aspects, and does not provide the same level of version control and code review functionality as GitHub.
Developer Community and Open Source Projects: GitHub has a large and active developer community. It serves as a hub for open source projects, allowing developers to contribute, discuss, and collaborate on various projects. TeamCity, while allowing integration with GitHub repositories, does not have the same level of community interaction or support for open source projects.
Extensibility and Customization: GitHub offers a wide range of integrations and plugins, allowing developers to extend its functionality and customize the platform to meet their specific needs. It has a rich ecosystem of third-party tools and services that can be easily integrated with repositories. TeamCity also supports integrations and plugins, but its focus is predominantly on its own build automation and deployment capabilities.
Pricing and Licensing: GitHub offers various pricing plans, including free options for open source projects, while also providing enterprise plans for larger organizations. It follows a subscription-based model and charges based on the number of users and private repositories. TeamCity, on the other hand, follows a perpetual licensing model where organizations can purchase and install it on their own servers. Its pricing is based on the number of build agents and concurrent builds.

In summary, GitHub provides a comprehensive platform for hosting, version control, and collaboration, while TeamCity focuses on continuous integration and deployment workflows with extensive build automation capabilities. GitHub has a strong developer community and offers extensive customization options, while TeamCity offers advanced build management features and a perpetual licensing model.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on GitHub, TeamCity

Anonymous

May 25, 2020

Decided

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

624k views624k

Comments

Weverton

CTO at SourceLevel

Jul 28, 2020

Review

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

944k views944k

Comments

Weverton

CTO at SourceLevel

Aug 3, 2020

Review

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

Pick the correct target branch
Make Drafts explicit
Name things properly
Ask help for tools
Remove the noise
Fetch necessary data
Understand Mergeability
Pass the message
Add screenshots
Be found in the future
Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

1.19M views1.19M

Comments

Detailed Comparison

GitHub	TeamCity
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.	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.
Command instructions; Source browser; Git powered wikis; Integrated issue tracking; Code reviews with inline comments; Compare view; Newsfeed; Followers; Developer profiles; Autocompletion for @username mentions	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;
Statistics
Stacks 295.6K	Stacks 1.2K
Followers 259.0K	Followers 1.1K
Votes 10.4K	Votes 316
Pros & Cons
Pros 1774 Open source friendly 1463 Easy source control 1254 Nice UI 1137 Great for team collaboration 868 Easy setup Cons 56 Owned by micrcosoft 38 Expensive for lone developers that want private repos 15 Relatively slow product/feature release cadence 10 API scoping could be better 9 Only 3 collaborators for private repos	Pros 61 Easy to configure 37 Reliable and high-quality 32 Github integration 32 User friendly 32 On premise Cons 3 High costs for more than three build agents 2 Proprietary 2 User-friendly 2 User friendly
Integrations
Grove Lighthouse Airbrake Codeship Bugsnag BugHerd Visual Studio Code HipChat CopperEgg Nitrous.IO	Slack

What are some alternatives to GitHub, TeamCity?

Bitbucket

Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.

GitLab

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

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.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

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.

Related Comparisons

GitHub vs TeamCity: What are the differences?

Introduction

Hosting and Collaboration Features: One major difference between GitHub and TeamCity is their focus on hosting and collaboration. GitHub provides a complete platform for hosting and managing repositories, allowing developers to conveniently collaborate and contribute to projects. On the other hand, TeamCity, while offering some limited code hosting capabilities, primarily focuses on continuous integration and deployment workflows.
Integration and Build Automation: TeamCity is specifically designed to facilitate the process of building, testing, and deploying software. It offers comprehensive build automation features, allowing developers to run builds on different platforms, control dependencies, and manage complex build workflows. GitHub, while providing some basic build features, does not have the extensive automation capabilities of TeamCity.
Version Control and Code Review: GitHub is renowned for its powerful version control system, Git. It offers advanced branching and merging capabilities, making it easier for developers to manage parallel development efforts. Additionally, GitHub provides built-in code review features, allowing teams to collaborate and provide feedback on code changes. In contrast, TeamCity focuses more on the build and deployment aspects, and does not provide the same level of version control and code review functionality as GitHub.
Developer Community and Open Source Projects: GitHub has a large and active developer community. It serves as a hub for open source projects, allowing developers to contribute, discuss, and collaborate on various projects. TeamCity, while allowing integration with GitHub repositories, does not have the same level of community interaction or support for open source projects.
Extensibility and Customization: GitHub offers a wide range of integrations and plugins, allowing developers to extend its functionality and customize the platform to meet their specific needs. It has a rich ecosystem of third-party tools and services that can be easily integrated with repositories. TeamCity also supports integrations and plugins, but its focus is predominantly on its own build automation and deployment capabilities.
Pricing and Licensing: GitHub offers various pricing plans, including free options for open source projects, while also providing enterprise plans for larger organizations. It follows a subscription-based model and charges based on the number of users and private repositories. TeamCity, on the other hand, follows a perpetual licensing model where organizations can purchase and install it on their own servers. Its pricing is based on the number of build agents and concurrent builds.

GitHub vs TeamCity

Overview