GitHub Actions vs TeamCity comparison

"We can trigger files manually or automate processes."

"I am familiar with the entire life cycle of the product."

"The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility."

"I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities."

"The most valuable feature of the solution is that it is a good product that offers stability and performance."

"It is easy to use, especially if you are accustomed to using GitHub."

"It improves efficiency as it involves no downtime and is managed by GitHub."

"GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools."

"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."

"TeamCity is very useful due to the fact that it has a strong plug-in system."

"It's easy to move to a new release because of templates and meta-runners, and agent pooling."

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."

"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."

"VCS Trigger: Provides excellent source control support."

"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."

"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."

"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."

"Sometimes incremental steps should be taken during deployment instead of trying to execute all tasks simultaneously, particularly when dealing with AWS EKS clusters and Helm charts."

"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex."

"My company would want to see some AI features in the tool as it can add value to the product."

"Switching between hosted and self-hosted agents can be a bit complex, as self-hosted agents need to be provisioned in platforms like Azure or AWS."

"GitHub Actions lacks a feature for automating the build process for mobile applications."

"In terms of improvements, I think better logging for debugging purposes would be helpful, especially for complex workflows."

"The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket."

"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."

"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly."

"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."

"REST API support lacks many features in customization of builds, jobs, and settings."

"I need some more graphical design."

"The upgrade process could be smoother. Upgrading major versions can often cause some pain."

"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."

"The tool's price is okay and reasonable."

"The product is slightly more expensive than some alternatives."

"The cost for GitHub Actions may be around $45 dollars per user."

"It's low-priced. Not high, but definitely low."

"For our basic usage, we didn't have to pay."

"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."

"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."

"It is free and open platform, so I would rate it 1 out of 10."

"The licensing is on an annual basis."

"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."