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.

    Government Administration

Great continuous integration tool for help promote better software development practices.

  • August 29, 2016
  • Review provided by G2

What do you like best about the product?
It is fairly easy to setup and start using right away, easy to setup permissions for different access levels.

Helps promote CI and has the ability to track history, notifications on events and monitor repositories for changes. Includes a windows system tray app to monitor in real time any events that you subscribe to.

Nice organization of projects and sub-projects with ability to create different builds for each project (Continuous Build vs Ad-hoc deployment builds)
What do you dislike about the product?
Sometimes the Agents stop running for unknown reasons, event logs show nothing out of the ordinary so we need to restart the windows service for things to happen again. There is no notification so it might fail and we will be unaware of it until someone takes notice.
What problems is the product solving and how is that benefiting you?
Help developers become away of issues when they check in code and are unaware that their changes have broken the build because they did not run tests locally. It also helps us schedule automated deployments to our integration environment weekly and ah-hoc deployments to our system test environments.
Recommendations to others considering the product:
Microsoft Team Foundation Server Build

    Industrial Automation

As a developer I use team city for building our code libraries.

  • August 27, 2016
  • Review provided by G2

What do you like best about the product?
Builds pretty quick and it has many options for connecting to several source control software. I also like the flexibility given with setting up build triggers.
What do you dislike about the product?
The user interface for team city could use an update.
What problems is the product solving and how is that benefiting you?
We use team city to build our product code. Our product is split into many libraries with many inter-dependencies. Team city allows us to automatically build our libraries in the correct order whenever we submit source code changes to your source control software. It also allows us to run automated unit tests on individual libraries, as well as smoke tests on our product build.
Recommendations to others considering the product:
I recommend this product for automated build/test environment with a continuous integration focus,

    Information Technology and Services

TeamCity is nice and intuitive for build and CI

  • August 03, 2016
  • Review provided by G2

What do you like best about the product?
Intutive, interface, quick and painless setup, more fun to use than Jenkins.
What do you dislike about the product?
No build configuration export, which is solved in latest version.
What problems is the product solving and how is that benefiting you?
We use it to build application releases and testing. It solved us a lot of time and efforts.
Recommendations to others considering the product:
Basically one of the best CI tool ever.

    Francesco M.

Paid continuous integration

  • July 19, 2016
  • Review provided by G2

What do you like best about the product?
Many options, Java based so easy to integrate a Maven project.

Coming from Jenkins I found TeamCity annoyingly complicated, even setting it up using docker was not easy.
What do you dislike about the product?
Bad documentation, difficult to find help Googling problems, cumbersome setup. I wanted my Jenkins back as soon as possible
What problems is the product solving and how is that benefiting you?
Build and deployment of a web application on different Tomcat server (for development, testing and production) using different Maven profiles.
Recommendations to others considering the product:
Check Jenkins before using TeamCity, if Jenkins is enough (probably it will be even more) for your requirements go with it and forget about TeamCity.

    Verified User in Computer Software

We use this for our CI builds

  • July 14, 2016
  • Review provided by G2

What do you like best about the product?
It provides a good way to setup builds, and run unit tests with github checkins. We have it setup to run unit tests for our mobile apps whenever someone submits a pull request to github.
What do you dislike about the product?
The github integration setup could be easier. It might be nice to just have pre-set check boxes to determine when you want something to be run, instead of using some branch syntax to determine that.
What problems is the product solving and how is that benefiting you?
This helps us build quality products since we are able to run unit tests each time a new commit is made. This helps us know up front if something in the commit is wrong rather than in production.

    Computer Software

TeamCity makes automated build easy.

  • May 20, 2016
  • Review provided by G2

What do you like best about the product?
TeamCity is such an improvement on the old XML-based build systems of the past. It has a user interface that makes the entire build process easier and integrates with all the relevant systems and source control providers and even allows you to use Amazon AWS to utilise the cloud for build agents.
What do you dislike about the product?
It can be somewhat daunting to a beginner but that is really more down to the power that it has and is based on the complexity of building software and all the various dependancies a software build has. There are worse interfaces out there and the help documentaion helps you manage this.
What problems is the product solving and how is that benefiting you?
Build automation via collecting your latest code from source control and all the depandanices needed to procuce the artifacts ready to actually deploy software to various environments.
Recommendations to others considering the product:
TeamCity is probably the easiest build server setup i have used and it has all the pieces needed to get the job done and is priced fairly and even has a freemium style pricing so you can kick the tyres on it.

    Christopher B.

A Solid All Around Automation Tool

  • May 19, 2016
  • Review provided by G2

What do you like best about the product?
TeamCity integrates better with .NET tooling than any other automation system out there. From it we can build our pull requests from GitHub, run our unit tests, deploy to integration servers and run our smoke tests. It hooks in well with other JetBrains tools (we use Reharper and DotCover) and logs in with domain credentials, keeping life simple.
What do you dislike about the product?
The configurations are not nearly as simple as they could be. When changing a setting, it is not always clear what is driven from the build master vs the build agent. It would also be much better if the program could update in place on its own, updates are a bit of a process.
What problems is the product solving and how is that benefiting you?
Before TeamCity, we did not have abny way of running our pull requests through a validation process. Now our code is all required to run and be tested on every commit. With the GitHub intergrations, we are even able to enforce that the tests are passing before the code moves forward. Our code is more stable and reliable thanks to TeamCity.

    Viacheslav S.

Powerful CI tool

  • April 27, 2016
  • Review provided by G2

What do you like best about the product?
Easy install.
Easy configuration.
No dependencies.
Support of NuGet, Powershell, NUnit.
Support of various VCS.
Ease of scalability via adding more agents.
Build Notifications are easily configured and always work fine.
Good for small teams and easily extended for big company via licensing.
What do you dislike about the product?
CodeCoverage is not available from the box as for TFS. To support Code Coverage, paid tools are required.
No other issues for my development requirements.
What problems is the product solving and how is that benefiting you?
Continuous integration.
Continuous testing
Complex deployment procedures.

    Larry R.

Great tool for managing builds and deploys

  • April 26, 2016
  • Review provided by G2

What do you like best about the product?
Totally flexible, but has good functionality out of the box. You can create your own processes and controls.
What do you dislike about the product?
Can sometimes be confusing how to figure out what you can or can't do.
What problems is the product solving and how is that benefiting you?
We are using this for managing builds and deployments. It has allowed us to make significant progress towards our goal of Continuous integration, and has liberated our devops team from the necessity of always being involved in every release at every stage.
Recommendations to others considering the product:
This tool is not for amateurs, but the amount of up front time you invest it getting it working is well worth it. It is important to understand what you want out of your development processes, and have a clear set of guidelines and process controls before you start. But if you have these, TC will make it possible for you to manage things flexibly and in a distributed manner.

    Connor H.

Most feature-complete CI server I've used

  • April 22, 2016
  • Review provided by G2

What do you like best about the product?
Once you've got TeamCity running you're just a few clicks away from the most pleasant setup experience around. You can easily extend the capabilities of your server by harnessing community developed plugins that are capable of just about anything, from running simple test suites to building games with the powerful Unity game engine.
What do you dislike about the product?
Compared to the setup of services such as Atlassian Bamboo, Jenkins and Travis CI, TeamCity can be a drag to configure. Whilst it certainly is worth it in the long run it's simply a lengthy inconvenience for those who are tasked with doing it.
What problems is the product solving and how is that benefiting you?
TeamCity is primarily used to automate the periodic execution of various test suites we write for our projects, recently we've decided to take it a step further and have TeamCity deploy built artifacts to our bug finding environment before letting the QA testers have their way.
Recommendations to others considering the product:
Make sure to take full advantage of the free trial, you should be able to cram as much testing as you need in to ensure it's the right product for you. If you are looking to work with a specific language then you should check out the available plugins before trying it to make sure that said language is actually supported.

showing 51 - 60