TeamCity Cloud

What do you like best about the product?

TeamCity’s build configuration feature helps me create standard build steps, and the same template can then be reused to set up different projects quickly. The VCS root feature is also easy to integrate and only requires a one-time setup, which helps connect with GitHub for incoming webhooks.

What do you dislike about the product?

The history for changing filters could be better, so it’s easier to review the exact changes that were made in different projects by someone else.

What problems is the product solving and how is that benefiting you?

It helps with designing the CI part end to end and triggering deployment jobs based on a GitOps strategy. The build steps provide robust ways to handle different product-specific use cases while designing a build job.

What do you like best about the product?

One of the best products built by JetBrains, and this is the only CI/CD platform for the present and future

What do you dislike about the product?

Was a little hard first time to shift, now all good

What problems is the product solving and how is that benefiting you?

It for sure solved the manual builds and deploys problem, so I push and it compiles, tests, and ships, saving my time. Controlled environment is good too

What do you like best about the product?

One thing that sets it apart from other modern CI tools—and what initially hooked me—is the GUI-based configuration. It makes it easy to configure, iterate, and experiment as you refine settings. That said, it can also become a bit of a drawback once you get really proficient with it.

It also has plenty of integrations. I haven’t run into a situation where I couldn’t find a plugin for something I wanted to do.

Performance has been quite good as well, with no complaints on my end.

The free tier is solid and enough to get a moderately sized team up and running. On top of that, being able to self-host the server and agents is a big plus.

What do you dislike about the product?

Pipeline as code isn’t as intuitive as it is in other competing tools. Also, containers used as runners don’t feel like first-class citizens.

What problems is the product solving and how is that benefiting you?

It covers most of our CI/CD needs. Being able to keep the CI configuration separate from the repo helps in certain use cases as well, so it feels like both a plus and a negative depending on the situation.

What do you like best about the product?

TeamCity is a highly flexible platform that allows for a deep level of customization, without being difficult for first-time use. The pricing is a bargain considering how essential it is for our team. Customer support has always been very prompt and helpful, and any questions or requests we've had have been answered quickly. It's quick and intuitive to set up a new pipeline, with lots of integrations included out of the box. At the same time, it provides tools for highly customized workflows and automation. Performance is always snappy, and so far, downtime has been nonexistent.

What do you dislike about the product?

Highly customized workflows can be difficult to set up, such as recipes, which can only be created and edited in-browser as raw XML. Cleanup rules are also difficult to understand and create.

What problems is the product solving and how is that benefiting you?

TeamCity allows our developers to know, at all times, whether their code is working across all of our teams and for all of our applications. It also enables to deploy new builds without any technical knowledge. With its integrations into item tracking applications, it provides proof of work and removes questions about whether a bug has been fixed or not. Before TeamCity, each of our software teams had to organize and track its work and its deployments, with each team coming up with its own system. This made it nearly impossible for management to track what was actually being done. With TeamCity, we now have a streamlined process that works for all of our teams, and actually gets utilized because it's easier than doing things any other way.

What do you like best about the product?

In general TeamCity is the best choice for our self hosted CI/CD pipelines.
UI/UX is very reasonable and functional for many use cases, like developers trying to run and monitor builds, QA trying to access build links etc. Admin functionality is good for most use cases which require new user setup, adjust permissions, configure server properties etc.
Most used integrations on our side are - ability to offload artifacts to AWS S3, cloud profiles for agents, integrations with artifacts servers docker, npm etc.
Performance is pretty good for amount of configurations we have (hundreds).
Pricing is on higher side but manageable by company of our size.
Also it is relatively easy to find information about Teamcity on internet or through AI in case if you stuck with some particular problem.
I don't have comprehensive opinion about AI tools integrated into Teamcity we just trying to learn what it is about.

What do you dislike about the product?

I think biggest issue we struggle with right now is ability to scale. With so many configurations and so many builds, UI becomes quite limiting for editing complex multi-step configurations. I see a lot of duplicated configurations, many team members still not grasped meta-runner concept. To put it simply we need unified development environment/UI with ability to quickly refer/edit meta-runners and deal with configuration/steps. Today we have a lot of configurations with awful amount of duplication or some legacy ways of how they do things and there is no clear way for us to refactor this.
Also management of Cloud profile Agents pose own challenges. Since most agents start as AWS AMIs, ability to keep them updated is a challenge now. With each TC server update agent software has to be updated as well, otherwise each time Agents start they will be updating agent software which increases time of startup dramatically.

What problems is the product solving and how is that benefiting you?

TC is our main CI/CD pipeline used by hundreds of developers and QAs across the globe and by different software product lines.

What do you like best about the product?

TeamCity have ability to integrate with verity of tools and streamline CD/DVD processes.IT is ease of use and flexibility to work.
Visual studio is enabling developers to start programming quickly.
Easy to read failure notices.

What do you dislike about the product?

Frizzing automatically, Manual restart is required to get start.
High Pricing model is biggest drawback.
only getting service resolved by support team, when raise incident for them.

What problems is the product solving and how is that benefiting you?

Performance is quite good. programming task is easy to perform.

What do you like best about the product?

While other tools often require a massive collection of third-party plugins just to perform basic tasks, TeamCity provides a polished, high-performance experience right out of the box

What do you dislike about the product?

The pricing model is often cited as its biggest drawback.

What problems is the product solving and how is that benefiting you?

TeamCity is essentially the “IDE of CI/CD servers.” It addresses pipeline fragmentation and the high maintenance overhead that often comes with it by offering a deeply integrated, intelligent environment that takes care of much of the heavy lifting for you.

What do you like best about the product?

It has basic features that meet a non-zero percentage of our testing needs.

What do you dislike about the product?

So many basic problems, it would take weeks to write them all out. Obvious examples:

1. No click zone on tiny buttons, so a click that falls within 1 pixel of a '...' button will hit the backing panel, causing chaos in the UI.
2. Triggering a build over the REST API requires setting the branch name twice, even though it would never make sense to set the branch name differently in one place than the other. What's worse, if you forget to set one of the branch name attributes, TeamCity proceeds with the build but marks it as a "default branch build", even if the other branch attribute clearly indicated a non-default branch.
3. Build agents are constantly going offline, or going into some mysterious frozen state, requiring manual restart (or worse). Is it really a problem for a cloud agent pool to sit idle for a few hours while remaining available to start agents on demand?

It appears there is no testing performed internally at TeamCity, and only the most severe issues reported by users are ever resolved. As a supposed contributor to progress in technological capability, JetBrains is a shocking failure, instead making a case for the regression of civilization wherever it is burdened with such pathological lack of work ethic. Sporting one of the most arrogant company names in modern history, employees in fact make no effort to "work smarter, not harder"; not even the most basic principles and techniques of computer science are applied in the TeamCity platform. Humanity is clouded by disappointment where companies like JetBrains disregard the work experience of anyone who relies on their products.

What problems is the product solving and how is that benefiting you?

Purportedly the product addresses automated testing and continuous integration requirements for software development organizations.

What do you like best about the product?

1. It gives us an opportunity for continuous integration of UNIT CASES
2. It gives us an opportunity for continuous DEVELOPMENT of UNIT CASES
3. It gives us an opportunity TO RUN OUR SYSTEM INTEGRATION TEST in pipeline using automation
4. It gives us an opportunity to run on a scheduler
5. It gives us an opportunity to get integrate with GITLAB or application like postman/ Intellij/ Eclipse
6. Easy implementation, not much complex
7. I am using it daily in my career as I am SDET

What do you dislike about the product?

I don't think we have any as such drawback as it fulfills the purpose

What problems is the product solving and how is that benefiting you?

1. It is helping us to build and deploy our code
2. It is helping us to run our UNIT CASES
3. It helps us to run automation regression packs

What do you like best about the product?

It supports .net framework and is an exceptionally reliable tool for freshers entering devops, you can run it on any operating system. Integrates with build/test tools seamlessly and keeps a record of history. Multiple Integrations with 3rd Party Applications like : JIRA - To track and report issues Visual studio - In enabling developers to start programming quickly. Docker- To automatically create containers

What do you dislike about the product?

API integration documentation Cost is high Resource usage is also high User interface can be improved Learning curve can be complex especially when you don't have support within your team. Customer support

What problems is the product solving and how is that benefiting you?

offers me as a developer continuous integration from all angles via a host of features. I can keep my code clean with remote run and pre-tested commits. It allows me to build and check code and then run automated tests on the server before any changes are committed. Easy integration with deployment tool like Octopus. Version control for code is another very important utility