--- description: 검증된 사용 후기를 확인하고 TeamCity 사용성, 특징, 가격, 장점과 단점에 대한 자세한 정보를 확인해보세요! 비슷한 경쟁 제품도 확인이 가능합니다. image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: TeamCity 가격, 사용 후기, 평점 | 켑테라 Capterra --- Breadcrumb: [홈](/) > [자동 테스트 소프트웨어](/directory/30609/automated-testing/software) > [TeamCity](/software/136011/teamcity) # TeamCity Canonical: https://www.capterra.co.kr/software/136011/teamcity Page: 1 / 3\ 다음: [Next page](https://www.capterra.co.kr/software/136011/teamcity?page=2) > TeamCity의 실시간 빌드 결과 및 지능형 테스트 보고를 활용해 복잡한 CI/CD 파이프라인을 자동화할 수 있습니다. > > Verdict: Rated **4.5/5** by 51 users. Top-rated for **추천 가능성**. ----- ## Overview ### TeamCity은(는) 누가 사용하나요? TeamCity는 팀의 성과를 개선하고 불필요한 추가 도구 관련 비용을 절감하려는 개발자 및 DevOps 엔지니어를 위해 고안되었습니다. ## Quick Stats & Ratings | Metric | Rating | Detail | | **종합** | **4.5/5** | 51 리뷰 | | 사용 편의성 | 4.1/5 | Based on overall reviews | | 고객 지원 | 4.2/5 | Based on overall reviews | | 비용 대비 가치 | 4.3/5 | Based on overall reviews | | 특징 | 4.3/5 | Based on overall reviews | | Recommendation percentage | 80% | (8/10 추천 가능성) | ## 공급업체 정보 - **회사**: JetBrains - **Founded**: 2000 ## Commercial Context - **시작 가격**: US$45.00 - **Pricing model**: (Free version available) (무료 체험판) - **Target Audience**: 자영업, 2~10, 11~50, 51~200, 201~500, 501~1,000, 1,001~5,000, 5,001~10,000, 10,000+ - **Deployment & Platforms**: 클라우드, SaaS, 웹 기반, Mac(데스크톱), Windows(데스크톱), Linux(데스크톱) - **Supported Languages**: 영어 - **Available Countries**: 그리스, 남아프리카, 네덜란드, 노르웨이, 뉴질랜드, 대만, 대한민국, 덴마크, 독일, 라트비아, 러시아, 룩셈부르크, 리투아니아, 마카오(중국 특별행정구), 미국, 벨기에, 벨라루스, 브라질, 스웨덴, 스위스 and 21 more ## 특징 - 계층 보기 - 구성 관리 - 디버깅 - 버전 제어 - 변경 관리 - 병행 실행 지원 - 보고/분석 - 소프트웨어 테스트 관리 - 워크플로 관리 - 지속적 배달 - 지속적 배포 - 테스트 스크립트 리뷰 - 품질 보증 ## Integrations (8 total) - Amazon EC2 - Docker - GitHub - Jenkins - Jira - Kantata - Microsoft Azure - Workspace ONE ## Support Options - 이메일/지원 센터 - FAQ/포럼 - 지식 기반 - 전화 지원 - 채팅 ## Category - [자동 테스트 소프트웨어](https://www.capterra.co.kr/directory/30609/automated-testing/software) ## 관련 범주 - [자동 테스트 소프트웨어](https://www.capterra.co.kr/directory/30609/automated-testing/software) - [지속적 통합 소프트웨어](https://www.capterra.co.kr/directory/31119/continuous-integration/software) - [구성 관리 도구 소프트웨어](https://www.capterra.co.kr/directory/32355/configuration-tools/software) ## 대안 1. [Jira](https://www.capterra.co.kr/software/19319/jira) — 4.4/5 (15345 reviews) 2. [GitHub](https://www.capterra.co.kr/software/129067/github) — 4.8/5 (6165 reviews) 3. [Jenkins](https://www.capterra.co.kr/software/171026/jenkins) — 4.5/5 (569 reviews) 4. [Datadog](https://www.capterra.co.kr/software/135453/datadog-cloud-monitoring) — 4.6/5 (358 reviews) 5. [Buddy](https://www.capterra.co.kr/software/157673/buddy) — 4.8/5 (176 reviews) ## 리뷰 ### "Best tool for build configuration,build history, and system maintenance in real time applications" — 5.0/5 > **shaik** | *2018년 3월 11일* > > **장점**: Every enterprise business uses this tool for maintaining their services enabled and establish the best business flow. All the services that are being build via Mule can be available via team city to be deployed.Its features include build history, user management and system maintenance. Build history has excellent feature of holding the various build version that are deployed earlier.Use service messages in your build scripts, interact via REST API, or create plugins for TeamCity using Open API. User Management has different ways of user authentication, and a log with all user actions for the transparency which can be used for tracking all activity on the server.Best feature is Version Control System(VCS) in which Team city in a single build it can take source code from different VCS Repositories.All the versions history is available environmental wise. > > **단점**: The least of this software is there are some additional features required for the versions to avail across different enviroments like manual build configurations process can be avoided for the lower environments and UI part can be increased looking for new enhancements ----- ### "Teamcity" — 5.0/5 > **Eric** | *2022년 5월 18일* | 부동산 | Recommendation rating: 10.0/10 > > **장점**: I am able to successfully manage over 600 projects in Teamcity in my environment. Updates are a breeze and downtime has been damn near zero in the five or six years I've used this product. The build configs are super flexible however I've not used another product so I'm not sure how my experience compares to the next. > > **단점**: I'm not a huge fan of the experimental UI for some views but for other items I prefer it. I'm often switching back and forth between the two UIs ----- ### "TeamCity makes a strong case against the potential of science and ingenuity to advance civilization" — 1.0/5 > **Byron** | *2026년 2월 18일* | 컴퓨터 및 네트워크 보안 | Recommendation rating: 0.0/10 > > **장점**: It is often usable for automated testing and continuous integration purposes, and supports a broad range of platforms including server, client and mobile. > > **단점**: 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. > > In our development department we use TeamCity on a daily basis for automated testing and continuous integration. ----- ### "Flexible and Integrative\!" — 4.0/5 > **Jitae** | *2025년 9월 30일* | 컴퓨터 소프트웨어 | Recommendation rating: 8.0/10 > > **장점**: They supports many Plugins which makes us to add more feature and can customize it based on our needs and easy to debug on each builds because it can display very details of each steps. > > **단점**: I used to like their UI which is pretty straightforward and easy to setup, but the most recent version of TeamCity now make it harder to change config/setting on projects. Also it does not support for parallel runs on a project. You have to wait for each builds to finish before running next one in a queue. > > Setting it up for each projects is pretty easy and TeamCity has good integration a tool like Git, which makes admin's life lot easier. So far its been a pretty smooth ride. haven't heard many complaints from Dev side. ----- ### "TeamCity - A platform to approach Continuous Integration and Delivery." — 5.0/5 > **Gurleen** | *2019년 2월 14일* | 정보 기술 및 서비스 | Recommendation rating: 9.0/10 > > **장점**: TeamCity by JetBrains is one of the best and simple tool to manage the build and Integration. The powerful integration features out of the box make it unique and operation team first choice. The DevOps approach helps in continuous Integration \& Delivery. Smart Configuration feature like project hierarchy, in-build templates, build chains \& dependencies split the build sequence in multiple step to serve in simplex form. The Version Control Systems integrate the process in comprehensive way. Build History is also helpful in tracking the issue \& let us allow in tracking the changes in the development process. Statistics of build history and test result help in generating the reports. > > **단점**: There are numbers of In-build configuration plugins for cloud integrations like Amazon, Azure, vSphere, Kubernetes and many more but cluster and creating the plugin for on-premises infrastructures is really a big and complex task to do with the TeamCity without the help of expertise. > > TeamCity By JetBrains provide the hassle free Continuous Integration \& Delivery. The freeware license come with up to 100 build configuration and 3 build agent are enough to check the feasibility study of your product. The powerful build CI \& smart configuration make it enterprise like DevOps tool. ----- Page: 1 / 3\ 다음: [Next page](https://www.capterra.co.kr/software/136011/teamcity?page=2) ## Links - [View on Capterra](https://www.capterra.co.kr/software/136011/teamcity) ## This page is available in the following languages | Locale | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | ko | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | sv | | ----- ## Structured Data