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:
giovannicandido uses Shippable
Very cheap and good quality integration service. Use docker as the underline infrastructure and is ready to deploy on many places like cloud foundry.
Its a build and reporter tool, continuous building the application
Packet uses Shippable
Shippable allows us to run our testing framework on the same exact images that we run our stack in. This helps us avoid any issues with the testing framework being different than the production framework.
saigkill uses TeamCity
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.