TeamCity vs. Go.CD vs. Strider
|
|
|
|||||
TeamCity |
Go.CD |
Strider |
|||||
Favorites25
|
Favorites32
|
Favorites6
|
|||||
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.
|
||||
Pros about this tool |
|
|
|
||||
Pricing |
|
||||||
Companies |
140 Companies Using TeamCity
|
20 Companies Using Go.CD
|
1 Companies Using Strider
|
||||
Integrations |
TeamCity
Integrations
|
No integrations listed yet
|
No integrations listed yet
|
||||
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
|
How developers use TeamCity vs Go.CD vs Strider
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
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.
saigkill uses TeamCity
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.
