The Shippable Blog

A Deeper look at Shippable Formations

Warning-Icon.png 

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.


 

We are very excited to announce the release of our new product line, Shippable Formations. Along with Shippable CI/CD, this is the first step in our journey towards enabling DevOps 2.0 - frictionless Dockerized pipelines from code to production without the need for any DevOps code or scripts.

Over the last several months, we've received a lot of feedback on our Shippable CI/CD product. One thing resonated above all - as customers start adopting Docker-based workflows and creating complex, multi-container applications, they were looking for something beyond CI/CD. Most of them were creating these workflows themselves, and this was taking valuable time away from what they really wanted to do, namely work on their product. 

As early adopters of Docker, we had created many internal workflows and processes that helped us ship faster. Shippable Formations is the productized version of all that we've learnt from shipping to production 5x-20x a day.

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. 

Post CI Dockerbuild

 
Warning-Icon.png
 

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.

container_build

We introduced our support for docker build a few weeks back - along with it's very own blog post - but we've had requests to support an additional workflow. Starting today, you can docker build an image post-ci. Before we go any further, EVERYTHING mentioned in blog mentioned above is a pre-req to do this. Make sure you do everything mentioned in that blog first, or your post-ci docker build won't work!

Some of you might be wondering why you'd ever want to do this. Well, post-ci building allows you to create a concise docker image that contains only what you need for deployment, and leave out anything that is only required for building/testing. After all, there really isn't a benefit to deploying your build tools to production! However, as there is no upfront way for us to know which files you’d like to put in your “prod” docker image, you must manually specify which files to include. Don't worry though, as it's a simple one-liner. We'll get that in a bit; you first need to tweak your project's settings a little bit further.

Caching containers to speed up your builds

Important update on this blog

IMPORTANT:

This blog is based on the old shippable.yml format. A built-in yml translator does translates the code from the old to the new format. Read more about the translation from the old to the new format here.

For the latest information, refer our documentation on caching and/or open a support issue, if you have questions.

 

Shippable IRC Notifications

Warning-Icon.png

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.


 

shippableIRC

We've talked about integrating with messaging services before, such as slack, but there are many more messaging services you can integrate Shippable with. Starting today, your minions can print out build status messages to IRC!

IRC support is implemented as a subtag of notifications. The IRC subtag itself has a number of subtags, but the two most useful one is the "channels" subtag. The channels tag is used to specify which IRC channels you would like your build to message.

The channels tag is quite easy to use, but let's show a quick example anyway! If you want your build to message the "shippable" channel on freenode, you would add the following snippet to your shippable.yml file:

notifications:
  irc:
    channels:
      - "chat.freenode.net#shippable"