The Shippable Blog

Abhijit Kini

Abhijit Kini
Find me on:

Recent Posts

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.

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 -

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.

Upgrading your Continuous Integration/Continuous Delivery subscription

Continuous Integration (CI) helps developers to speed up the application development life cycle by automating build, test and deployment of the application. Continuous Delivery (CD), helps developers in shipping code from source control systems to the production environment.

You can have both CI and CD, for free, by using Shippable.In this tutorial, I'll go over what's available for free, when you need to upgrade and how to upgrade.