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

"We can trigger files manually or automate processes."

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

"It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."

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

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

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

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

"TeamCity is a very user-friendly tool."

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

"Good integration with IDE and JetBrains products."

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

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

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

"The integration is a valuable feature."

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

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

"Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."

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

"GitHub sometimes makes it difficult to debug actions."

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

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

"Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows."

"The minor drawback of GitHub Actions is the management of the dashboard and pipeline runs, which needs improvement. The dashboard for running pipelines could be better."

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

"I need some more graphical design."

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

"If there was more documentation that was easier to locate, it would be helpful for users."

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

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

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

"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 product is slightly more expensive than some alternatives."

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

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

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

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

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

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

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