The CI/CD and DevOps Blog

Learn about various tried-and-tested strategies that will help you ship code faster

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.

Our journey to microservices: mono repo vs multiple repositories

Microservices are currently the hottest topic in software development. The concept is simple: Break down your application into smaller pieces that each perform a single business function and can be developed and deployed independently. These pieces, commonly called services, can then be assembled into an application using some flavor of service discovery like nginx or consul. The microservices approach is considered the architecture of choice for teams that want to build scalable platforms and efficiently and rapidly innovate on them. 

As infatuated as I am with this architecture, our journey to microservices was a long and winding road. It has finally led us to a version of the architecture that gives us the scalability and agility we require as a business. I want to share my thoughts, experiences, and lessons learned in a series of blogs around this topic so you may benefit from our experiences. Also, I would love to get your feedback or comments on our approach.

When you start moving to microservices, the first question before you write a single line of code is: How do you organize your codebase? Do you create a repository for each service, or do you create a single ‘mono repo’ for all services? The two approaches are illustrated below:

Getting started with Docker Datacenter

Docker Datacenter is an integrated, end-to-end platform for enterprise-grade agile application development and management from the data center to the cloud.

The core concept of Docker Datacenter is Containers as a Service (CaaS), where organizations can deploy and manage container-based applications on-premises or in a virtual private cloud. A CaaS provides an IT-managed and secured application environment of platforms and infrastructure where developers can build and deploy applications in a self-service manner.

Docker Datacenter (DDC) is a great choice for organizations looking for a CaaS Platform with built-in enterprise-class support. DDC includes support for High Availability and Security, LDAP/AD integration and a Docker Swarm-based cluster management solution, which treats the entire cluster as a single, virtual Docker Host. In this blog, I will show you how to create an end-to-end application delivery workflow for Docker Datacenter. The workflow will use CI and CD in Shippable to take an application from the developer code repository to deployment in Docker Datacenter.

Shippable Now Integrates with Docker Datacenter

Today at the Docker Roadshow in Chicago, Shippable's Tom Trahan announced our latest integration, this time in support of Docker Datacenter. Shippable has been tightly integrated with Docker since day 1, and Docker Datacenter support is the latest connection we have built for the Docker platform. Docker Datacenter joins our Docker Cloud integration to give customers the most flexible choices for CI pipelines on-prem or in the cloud.