A good continuous integration and deployment solution integrates seamlessly with customer workflows and acts like an invisible helper (for the most part) to ensure that the codebase is always deployable. Shippable strives to do just that. Users are notified about build status in their Inbox and they can change config settings by changing a few lines in the shippable.yml file in their repository. All without coming to the Shippable UI.
Today, we have enabled a significant scenario which will help further this philosophy - support for the GitHub commit status API.
In April 2013, Shippable launched a Jenkins based CI using virtual machines (VMs). Our plan was simple - take the open source Jenkins, host it in the cloud, and start making money. After all, why would developers spend the time, effort, and money to set it up and maintain it when we were doing it for them for a few dollars a month?