The Shippable Blog

Shippable offers OpenShift customers blazing fast CI/CD service

Shippable is pleased to announce that we now offer OpenShift customers our blazing fast, hosted CI/CD service. OpenShift customers can now choose the simplicity of using a true SaaS solution instead of spending the Gears to host a CI server themselves (not to mention further engineering time configuring and maintaining their CI system).
Shippable will (soon) be available through RedHat's OpenShift Marketplace.
You can try Shippable's service (in BETA) on OpenShift right now at openshift.shippable.com

Build status is now integrated with GitHub pull requests!

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. 

Why Shippable is All In on Docker

 

 

 

 

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?

Right? Nope.

Have container...will ship (or why Shippable uses containers)

carrying-containers

Recently, Shippable was listed in the top 10 startups built on docker. Of the top 10 startups listed, Shippable is the only startup using Docker to do continuous integration and deployment.

Docker of course, is the open source Linux container engine and in a future post, we will talk about why Shippable chose Docker.