The CI/CD and DevOps Blog

DEPRECATED BLOG:

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

Shippable uses Slack on a daily, continuous basis for all team communication. Why, you ask? Because it allows us to "work in the moment". We have found it to be significantly more efficient, more transparent and faster to communicate using Slack. And less email!

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 super excited to announce support for Quay.io integration on the Shippable platform! Many of you requested this and we agree, it's a great service. Quay.io offers a wonderful user experience with detailed information about your images. And, of course, Shippable provides you multiple options to tag images generated via Shippable CI/CD, making it easy to trace those images from the registry back through all activities that occurred to build and validate them. While we were at it, we also added support to integrate any private registry on Shippable. 

This post will walk you through how to integrate your Shippable Account with Quay.io and push and pull images through Quay.io.

Here at Shippable we love taking customers all the way to continuous deployment. We've detailed a variety of different ways to get there in the past, and today we are going to be bringing out yet another way. Today we'll be showing you how to trigger your Shippable builds, to push your rails apps to Engine Yard.

Before going any further, there are a few pre-reqs:

• An active Engineyard account
• A working rails app on github
• An active Shippable account
• The above rails app being enabled on Shippable
• An application env already setup on Engine Yard

DEPRECATED BLOG:

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

In our last post we discussed using the Shippable API to manually interact with your project through the terminal. That's cool and all... but poking APIs with curl is a little old-fashioned. Let's take it up a level. Today, we are going to show you how to plug Slack's external webhooks into our API. After doing this you can monitor your build status, trigger builds - whatever you desire - all from the comfort of your team's Slack channel!

Some of you might recall that we have talked about slack integration before in DevOps Notifications: A Simple Way to Use Slack with Shippable. You might be wondering, "Wait... If I could already integrate with Slack, how is this different from before?! How is this a new feature?" Great question! So, before we were using Slack's incoming webhooks feature; our app could talk to Slack, but there was no way for Slack to communicate back to our app. With our new API, you can now have one-way or two-way communication between Slack and your minions.

Looking to configure a continuous deployment to Digital Ocean for a Node.js app? Tired of manually trying to configure git hooks to work with you? Is SCP just a little too old fashioned and clunky. Great news! Your search is finally over as today we'll show you how to combine Shippable and Dokku to fit your deployment needs!

Dokku describes itself as a 'docker powered mini-heroku' and it lives up to the claim! With Dokku installed on your droplet, you can interact with it very similarly as to how you would a heroku app. By orchestrating Docker, Buildstep, and Gitreceive  together, Dokku forms a simple, not to mention well functioning, roll your own PaaS. More information on Dokku can be found here.