TeamCity vs. Go.CD vs. Strider
|
|
|
|||||||
|
|
|
|
|||||||
Hacker News, Reddit, Stack Overflow Stats |
|||||||||
GitHub Stats |
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 Go.CD?GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.
|
What is Strider?Strider is an Open Source Continuous Deployment / Continuous Integration platform. It is written in Node.JS / JavaScript and uses MongoDB as a backing store. It is published under the BSD license.
|
||||||
Want advice about which of these to choose?Ask the StackShare community! |
|||||||||
Pros |
|
|
|
||||||
Cons |
|
|
|
||||||
Pricing |
How much does TeamCity cost?
|
How much does Go.CD cost?
|
How much does Strider cost?
|
||||||
Companies |
What companies use TeamCity?
216 companies on StackShare use TeamCity
|
What companies use Go.CD?
31 companies on StackShare use Go.CD
|
What companies use Strider?
3 companies on StackShare use Strider
|
||||||
Integrations |
What tools integrate with TeamCity?
12 tools on StackShare integrate with TeamCity
|
No integrations listed yet
|
No integrations listed yet
|
||||||
What are some alternatives to TeamCity, Go.CD, and Strider?
|
|||||||||
Latest News |
TeamCity 2018.2.2 is released
January 23, 2019
New in TeamCity 2018.2: Simplified Installation of P...
January 21, 2019
New in TeamCity 2018.2: Show Kotlin DSL for Build Co...
January 17, 2019
|
||||||||
Related Comparisons
Interest Over Time
Reviews of TeamCity, Go.CD, and Strider
How developers use TeamCity vs Go.CD vs Strider
-
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
-
saigkill uses TeamCity
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.
-
-
