GitHub Actions vs TeamCity comparison

"It is a very stable solution as we have not faced any issues."

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

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

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

"We can trigger files manually or automate processes."

"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."

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

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

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

"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 a very user-friendly tool."

"Good integration with IDE and JetBrains products."

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

"VCS Trigger: Provides excellent source control support."

"The UI could be better."

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

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

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

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

"GitHub sometimes makes it difficult to debug actions."

"The reporting capabilities are somewhat limited."

"There could be more integration options with different platforms."

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

"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 upgrade process could be smoother. Upgrading major versions can often cause some pain."

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

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

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

"I need some more graphical design."

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

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

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

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

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

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

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

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