The CI/CD and DevOps Blog

Manisha Sahasrabudhe

Manisha Sahasrabudhe

Recent Posts

The great DevOps 2.0 debate of 2015

 

Welcome to the great DevOps 2.0 debate! The topic under discussion is - Why is Shippable calling themselves a DevOps 2.0 platform? 

We love Twitterstorms as much as the next person. After all, who can forget the epic exchange between John Legere and The Donald? Or closer to home, the banter between Docker's @shykes and the Coreos folks? Everyone loves a good old-fashioned flame war.

Our announcement on Wednesday ruffled some feathers, albeit important ones. We said that our new product line, Shippable Formations, delivers what we are coining as a DevOps 2.0 platform. And then all hell broke loose. Even Patrick Deboisthe Father of DevOps, was confused and skeptical - 

Patrick's tweet about our DevOps 2.0 announcement 

There was a lot of this going around.

DevOps 2.0 is here - Announcing Shippable Formations and enhanced CI capabilities

 

We are excited to announce the release of significant enhancements to Shippable Continuous Integration and the introduction of a new product, Shippable Formations. Together, these two products transcend traditional DevOps and take it to the next level, to DevOps 2.0. 

DevOps 2.0 - Frictionless pipelines from code to production

Monitor your upstream Docker image dependencies with Lighthouse

Have you ever wasted your time debugging a broken build only to realize a few frustrated hours later that it was due to something that changed in one of the images you depend on?

Lighthouse to your rescue!

Lighthouse is available to all Shippable users for free! Using this feature, you can 'watch' any public Docker image or any private image you have access to from any registry and get notified via email when that image is updated. 

Immutable containers with version tags on Docker Hub

 Immutable containers with version tags on Docker Hub

Lately, several folks have asked us about our reasoning behind adding build numbers as the version tags for Docker Hub images. Briefly, our current flow is -

- Pull code from GitHub
- Pull image from Docker Hub (or build from a Dockerfile)
- Run CI in the container
- If CI passes and push to Docker Hub is configured in the yml or Project Settings, push image to Docker Hub with a version tag <image name>:<build number>

The question is - why don't we just tag the image with <image name>:latest? What is the value behind versioning images?

Important: Change in GitHub scopes for Shippable

We recently found a bug that prevented us from deleting webhooks on GitHub when a user who had only authorized Shippable for public repositories deleted a project on Shippable. The root cause of this bug is that we have write:repo_hooks scope for public repositories, and this does not include permissions to delete a webhook. From GitHub documentation https://developer.github.com/v3/oauth/#scopes -

github_docs

Who is affected by this?

Existing users who have authorized Shippable only for GitHub public repos.