TeamCity vs wercker: What are the differences?
Developers describe TeamCity as "TeamCity is an ultimate Continuous Integration tool for professionals". 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. On the other hand, wercker is detailed as "Build, test, and deploy container-native applications". Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
TeamCity and wercker can be categorized as "Continuous Integration" tools.
Some of the features offered by TeamCity are:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
On the other hand, wercker provides the following key features:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
"Easy to configure" is the top reason why over 52 developers like TeamCity, while over 34 developers mention "Automatic Deployments" as the leading cause for choosing wercker.
Stack Exchange, ebay, and Apple are some of the popular companies that use TeamCity, whereas wercker is used by FashionUnited, Hazeorid, and Wantedly. TeamCity has a broader approval, being mentioned in 171 company stacks & 51 developers stacks; compared to wercker, which is listed in 40 company stacks and 23 developer stacks.
What is TeamCity?
What is wercker?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using wercker?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
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
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.