Sign in
Sign in
or
Create a new account
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

TeamCity Cloud

JetBrains Americas

Reviews from AWS customer

0 AWS reviews
  • 5 star
    0
  • 4 star
    0
  • 3 star
    0
  • 2 star
    0
  • 1 star
    0

External reviews

64 reviews
from

External reviews are not included in the AWS star rating for the product.

    Arbi A.

TeamCity is awesome you should use it if you're into continous integration

  • April 20, 2016
  • Review provided by G2

What do you like best about the product?
I previously worked for a software company that develop JEE applications. We had TeamCity for continuous integration and building. What we liked about it was the quality of the tool and even it's not a free one (although you can a limited environment for free package that includes the TeamCity CI server and three build agents) the paid support behind it. But even if it cost money, it's price is still affordable compared to Microsoft products (we had one .Net developer that used Visual Studio). We also liked one neat feature in TeamCity which is the web-based dashboard. It gave us a quick overview of our project status, additional to reporting information that can be convenient for a various kind of users and anyone involved in the project. It also gave us the build progress, ability to get more details with a drill down approach, in addition to historical data on the projects and configurations to keep an eye on changes.
What do you dislike about the product?
May be the fact that it is not an open source project. We, especially in the java ecosystem, used to open source, we use other people work and give back to the community whenever it is possible.
What problems is the product solving and how is that benefiting you?
We used TeamCity for continuous integration of JEE applications, and to keep track on the how development is evolving and regression tests. We also made benefit of the code analysis built-in feature.
Recommendations to others considering the product:
Give a try to TeamCity and you'll like how cool it is:
- TeamCity is extremely easy to setup, configure and use.
- TeamCity is deeply integrated with a lot of tools and technologies without need for complicated configurations,
- TeamCity is not that expensive compared to any commercial dev tools out there,
- TeamCity is secure,

    Transportation/Trucking/Railroad

Decent CI/CD Software

  • April 08, 2016
  • Review provided by G2

What do you like best about the product?
It was very easy to setup. The interface is logically laid out. It supports a number of nice features including automated tests, dependency checks, support for many different code repositories including cvs and svn, and requires only occasional maintenance.
What do you dislike about the product?
It doesn't integrate with our other Atlasssian products as nicely as Bamboo does. Which to be fair is expected as Bamboo is also an Atlasssian product. Builds will typically generate a fair amount of files and artifacts which can quickly consume disk space. The cleanup routines within Teamcity need to be carefully tuned to avoid filling your disks. This can become an onerous task.
What problems is the product solving and how is that benefiting you?
We were looking for a good continuous integration, testing, and deployment server
Recommendations to others considering the product:
TeamCity is roughly equivalent to Jenkins and Bamboo. With Jenkins it's very extensible but will require more manual configuration and fiddling versus TeamCity and Bamboo which are both polished commercial products. If you are already using Atlasssian products, you'll gain better integration by using Bamboo. If you aren't an Atlasssian shop, then TeamCity offers similar functionality. You'll need to make your decision based on current features, UI, and prices for each.

    Jonathan E.

The easiest-to-use and most feature-complete CI server you can find

  • March 29, 2016
  • Review provided by G2

What do you like best about the product?
Once TeamCity is up and running, configuration for projects and builds is a breeze. Community-provided plugins allows us to easily expand functionality (such as the Unity Runner for building Unity projects, or the SFTP Deployment plugin to handle deployments over SFTP). When compared to its alternatives, TeamCity's UI is both functional and aesthetically pleasing.
What do you dislike about the product?
Initial installation/setup was not as smooth as some of the competition, which makes upgrading TeamCity a somewhat cumbersome process. As a result, we rarely upgrade unless a new release fixes a blocking or nuisance issue.

Built-in support for various languages is quite lacking. The bulk of our projects' build steps are shell scripts. Building projects using ant or MSBuild is incredibly easy, but for many other languages (for us, mainly Python) the initial setup of your build configuration can be a bit daunting.
What problems is the product solving and how is that benefiting you?
We use TeamCity to perform automated tests and, most recently, automated deployments to our staging environments. By removing the need for us to perform deployments manually, a bulk of our time has been freed up for other tasks.
Recommendations to others considering the product:
TeamCity's free license should be sufficient for an organization of any size to give the system a try and see if it will meet all business requirements.

    Michael J.

An excelent and configurable CI server

  • March 08, 2016
  • Review provided by G2

What do you like best about the product?
TeamCity is a very flexible CI server. It can work with nearly any language or build system, provided the tools are present and can be run in a "headless" manner. Since the build process uses agents that can be installed remotely and on different operating systems, a single TeamCity server can be used for cross-platform development. Build steps are completely configurable and can range from built-in steps (MSBuild, Ant, etc) to scripts, to "meta-runners". It also supports displaying code coverage information, test output and VCS history.
What do you dislike about the product?
The largest problem with TeamCity is that it's very memory-hungry. Expect to devote a server to the service if you're going to use it. It's coded in Java (like nearly all of JetBrains' other tools) on top of the Tomcat servlet engine. It's also just slightly custom enough that running it on a vanilla Tomcat install is very painful.
What problems is the product solving and how is that benefiting you?
With a large, distributed team working on a complex project, it's very important to keep code quality in check. Automating tests and deploying to a QA testing environment helps keep turnaround fast and allows our developers to get quicker feedback on their code. TeamCity gives us confidence that our code will build and run properly.
Recommendations to others considering the product:
There are a lot of CI solutions out there. TeamCity works best when you can self-host the system and have the in-house knowledge to maintain it. It may also be a great value as many services, such as Visual Studio Team Services can get expensive when you have complex and long-running build processes. TeamCity also has a no-cost license level, which is great for trial or usage by small companies.

showing 61 - 64