The CI/CD and DevOps Blog

Deploy your first Continuous Deployment Pipeline

As you know, we released our new implementation of continuous deployment pipelines last month. While our basic documentation is up to date, we believe that learning the new pipelines is best done with quick tutorials that demonstrate the power of CD and how easy it is to get started.

We have created a sample project and sample configuration to deploy the project to test environment,  create a release with semantic versioning, and deploy the project to production. The entire end to end scenario should take less than 30 mins to try out and while you won't learn every little trick, it will definitely make you comfortable with the configuration and how to set things up.

So read on and try it out!

How to deploy to Elastic Beanstalk (Part 2)

In the previous part, we went over the steps of source code deployment to AWS Elastic Beanstalk using a simple Node.js app. We deployed the source code natively at first, then compared with deploying it through Shippable. The latter approach showed actions in the work flow executed automatically for you, by Shippable's unified CI/CD platform.

I'll take a similar approach for this part where we'll go through a deployment of a Docker container of a Node.js app to AWS Elastic Beanstalk. To fully understand this tutorial, complete the previous source code deployment to AWS Elastic Beanstalk first.

A Guide to Modern Application Delivery Nirvana

Containers. Continuous Integration. Microservices. These are among the leading buzzwords of modern application delivery.

Yet like most buzzwords, these terms can be pretty enigmatic -- especially if you haven't yet made the jump to a Continuous Delivery-based workflow.

Customize environments for different branches of a Continuous Integration project

There have been several requests on our support forum on how to customize environments to specific branches while running Continuous Integration (CI) builds for a repository that has multiple branches. In this tutorial, I'll go over a common scenario and review the multiple ways we can configure branch-specific actions during the CI build. 

The scenario I use for this tutorial is, to pull a Docker image in the CI process and upon completion, use different tags for the branches when pushing the Docker image to Docker Hub. The Docker tags should be customized to the specific branch where the CI was processed and should include the build number. The final results of successful CI process tagging different branches looks as shown.

Our Insider's Guide to Seattle for DockerCon16 visitors

Next week, DockerCon16 comes to our hometown of Seattle. Shippable is excited to be a sponsor of DockerCon16 and to welcome the Docker community to our neighborhood. For visitors to the conference, we have gathered some of our team's favorite tips and things to do in Seattle so you can get the most out of the event. And, if you want to get even more insider info, come and visit the Shippable booth and ask any of us for our favorite haunts and suggestions so you can maximize your down time in the Jet City.