GitHub Actions vs TeamCity

Need advice about which tool to choose?Ask the StackShare community!

GitHub Actions

1.5K
384
+ 1
17
TeamCity

1K
898
+ 1
307
Add tool

TeamCity vs Github Actions: What are the differences?

TeamCity: TeamCity is an ultimate Continuous Integration tool for professionals. 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; Github Actions: Automate your workflow from idea to production. 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.

TeamCity and Github Actions belong to "Continuous Integration" category of the tech stack.

Some of the features offered by TeamCity are:

  • 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

On the other hand, Github Actions provides the following key features:

  • Multiple workflow files support
  • Free and open source
  • Workflow run interface

Craftbase, Accenture, and ebay are some of the popular companies that use TeamCity, whereas Github Actions is used by Craftbase, Rainist, and Walls.io. TeamCity has a broader approval, being mentioned in 274 company stacks & 527 developers stacks; compared to Github Actions, which is listed in 39 company stacks and 60 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of GitHub Actions
Pros of TeamCity
  • 4
    Free
  • 3
    Easy to duplicate a workflow
  • 2
    Read actions in Marketplace
  • 2
    Integration with GitHub
  • 2
    Ready actions in Marketplace
  • 1
    Active Development Roadmap
  • 1
    Fast
  • 1
    Configs stored in .github
  • 1
    Docker Support
  • 60
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    Github integration
  • 31
    On premise
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 4
    REST API
  • 4
    Great support by jetbrains
  • 4
    Fully-functional out of the box
  • 4
    Projects hierarchy
  • 4
    Chain dependencies
  • 3
    100+ plugins
  • 3
    Free for small teams
  • 3
    Per-project permissions
  • 3
    Personal notifications
  • 3
    Build templates
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Smart build failure analysis and tracking
  • 2
    Upload build artifacts
  • 2
    Artifact dependencies
  • 2
    Build progress messages promoting from running process
  • 1
    TeamCity Professional is FREE
  • 1
    Powerful build chains / pipelines
  • 1
    Built-in artifacts repository
  • 1
    Repository-stored, full settings dsl with ide support
  • 0
    Official reliable support
  • 0
    High-Availability
  • 0
    Hosted internally

Sign up to add or upvote prosMake informed product decisions

Cons of GitHub Actions
Cons of TeamCity
  • 5
    Lacking [skip ci]
  • 4
    Lacking allow failure
  • 2
    Lacking job specific badges
  • 1
    No ssh login to servers
  • 1
    No Deployment Projects
  • 1
    No manual launch
  • 1
    Proprietary
  • 1
    High costs for more than three build agents
  • 1
    User friendly
  • 1
    User-friendly

Sign up to add or upvote consMake informed product decisions

What is 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.

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!

What companies use GitHub Actions?
What companies use TeamCity?
See which teams inside your own company are using GitHub Actions or TeamCity.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with GitHub Actions?
What tools integrate with TeamCity?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to GitHub Actions and TeamCity?
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.
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.
Azure Pipelines
Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.
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.
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.
See all alternatives