The CI/CD and DevOps Blog

7 things to consider while moving to a microservices architecture

In part I of my four part blog series on Microservices, I explained what microservices are and the benefits you will see by adopting this architecture.

However, life is all about tradeoffs. In part II of this series, I will go over the things you need to consider while moving to microservices, as well as some challenges that crop up even when you do everything right.

Microservices for greenfield projects

Anytime your team develops a new application from scratch, it feels great not to inherit technical debt and be locked into outdated decisions made years ago.  Most teams developing new apps today would probably choose to containerize them using Docker and adopt microservices architecture for speed and agility.

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!

Customizing build badges to display a Node.js project status

Badges are often a convenient utility to track the status of a software project. One can configure a badge to show the project's last build status in a convenient location. Shippable provides its own API for badges. This API has default badges for pending completion, failed & successful builds.

In the previous tutorial, I configured a build badge for a Node.js project on Shippable. However, I would like to customize the build badge display to my specifications by changing the color and label of these badges. In this tutorial, I'll walk through customizing these badges to achieve the same by using a third party service - shields.io.

Slack, Elastic Beanstalk & UI changes highlight the 7/1 Service Update

On Friday, July 1 evening Pacific time, Shippable's build platform went through a scheduled service update. There are four main changes implemented as part of this update. They are:

  1. Slack Configuration
  2. AWS Elastic Beanstalk Configuration
  3. Fixed the timeout bug
  4. Re-vamped UI

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.