At Codeship we run immutable servers which we internally call Checkbot. These are the machines responsible for running your tests, deploying your software and reporting the results back to our web application. Of course, there are constant changes ...

When developing a new product and finding that product market fit every team needs to move fast. Especially startups, as the whole future of the company is dependent on quickly finding the people who pay for your product.

UPDATE: We are delighted that Mitchell Hashimoto, the creator of Vagrant and Packer, shared our blog post and recommended reading it. We tweet to share the love!

UPDATE:We’ve added performance comparisons done by Jonathan Rochkind to the additional links. He had Puma come out on top as well.

Signing up for a new service is exciting. You are interested enough that you think the service will help you. It has every feature that you missed so dearly in your current tools. You tell your colleagues how great working with this service will be. ...

Quick iteration is key to develop a new product and finding the product-market fit. When we started Codeship it was clear that we needed to automate as much as we can. Otherwise we wouldn’t be able to succeed with a small team.

Last week we talked about Deployment Pipelines and Zero Downtime Deployment.

Last week we talked about how we review code, open pull requests and use Github issues to manage our development workflow.

Last week we showed you how we start with a new feature and the workflow to implement it. This week we will focus on the steps necessary to get your feature ready to be shipped.

Today we have a guest post from Florian Motlik of Codeship. This blog post kicks off a new series about how the Codeship team works on Codeship, starting with how they develop new features.

Here at Codeship we always strive to find the best ways to test our application before we go live. We need to have all the necessary tests and tools in place to make sure our application works.