GitHub Actions vs TeamCity comparison

"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."

"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."

"GitHub Actions is a beautiful tool that integrates smoothly with all major tools, reducing CI/CD work by 30% to 40%."

"The product's most beneficial feature is the ability to create workflows within the solution."

"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."

"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."

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

"It is user-friendly, with clear and organized processes, making it easy to navigate and work with."

"VCS Trigger: Provides excellent source control support."

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

"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."

"TeamCity is more structured and user-friendly than other vendors."

"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."

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

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

"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."

"The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly."

"We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter."

"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."

"The reporting capabilities are somewhat limited."

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

"The UI could be better."

"It will benefit this solution if they keep up to date with other CI/CD systems out there."

"The integration between other solutions and TeamCity could be smoother."

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

"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."

"I need some more graphical design."

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

"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."

"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."

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

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

"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."

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

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

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

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

"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."

"The licensing is on an annual basis."