TeamCity vs. Semaphore
|
|
|||||
|
|
|
|||||
Hacker News, Reddit, Stack Overflow Stats |
||||||
GitHub Stats |
No public GitHub repository stats available
|
No public GitHub repository stats available
|
||||
Description |
What is TeamCity?TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
|
What is Semaphore?Whenever somebody pushes new code to GitHub, Semaphore immediately runs all tests on the corresponding branch. Every time you create a new branch, Semaphore builds it automatically. It also knows how to clean up when you delete it.
|
||||
Want advice about which of these to choose?Ask the StackShare community! |
||||||
Pros |
|
|
||||
Cons |
|
|
||||
Pricing |
How much does TeamCity cost?
|
How much does Semaphore cost?
|
||||
Companies |
What companies use TeamCity?
218 companies on StackShare use TeamCity
|
What companies use Semaphore?
46 companies on StackShare use Semaphore
|
||||
Integrations |
What tools integrate with TeamCity?
12 tools on StackShare integrate with TeamCity
|
What tools integrate with Semaphore?
12 tools on StackShare integrate with Semaphore
|
||||
What are some alternatives to TeamCity and Semaphore?
|
||||||
Latest News |
The official TeamCity Azure Resource Manager template
February 12, 2018
TeamCity 2017.2.2 is released
January 31, 2018
Branch specific settings in TeamCity
January 23, 2018
|
Daily API RoundUp: Flinks, Semaphore CI, ReadyCloud
August 12, 2017
|
||||
Related Comparisons
Interest Over Time
Reviews of TeamCity and Semaphore
How developers use TeamCity vs Semaphore
-
DigitalPermits uses TeamCity
TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.
-
Stack Exchange uses TeamCity
TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:
- Tell HAProxy to take the server out of rotation via a POST
- Delay to let IIS finish current requests (~5 sec)
- Stop the website (via the same PSSession for all the following)
- Robocopy files
- Start the website
- Re-enable in HAProxy via another POST
-
danlangford uses Semaphore
The Bitbucket integration with branch whitelists allows you to conserve your 100 builds this month.
-
saigkill uses TeamCity
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.
-
-
-
