GitHub Actions vs TeamCity comparison

"We can trigger files manually or automate processes."

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

"GitHub Actions is valuable for its ease of use and integration."

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

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

"I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations."

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

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

"Good integration with IDE and JetBrains products."

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

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

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

"TeamCity is a very user-friendly tool."

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

"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

"TeamCity's GUI is nice."

"In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process."

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

"The reporting capabilities are somewhat limited."

"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 it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."

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

"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 sometimes makes it difficult to debug actions."

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

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

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

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

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

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

"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."

"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 cost for GitHub Actions may be around $45 dollars per user."

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

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

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

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

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

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