Posted by Tom Trahan

shutterstock_225083608

We are very excited to announce support for Google Container Registry (GCR) integration with Shippable’s CI/CD cloud platform!

Our support for building and deploying Docker-based applications combined with Google's new private registry service make this a fantastic combination for anyone looking to accelerate their Docker development efforts.  

Many of you already use our custom workflows for Docker applications that let you quickly move from committing code changes to having validated Docker images ready to deploy.  With Google Container Registry (GCR), you can now manage those Docker images with secure, private Docker image storage on Google Cloud Platform, known for consistent uptime and security.  Additionally, GCR provides additional benefits we think you will like, such as fine grained access control, server-side encryption of images, and super fast deployment to Google Container Engine and Google Compute Engine.  Once stored in GCR, you can easily access the images from any machine for use in a variety of scenarios, including deploying to Google Compute Engine (GCE) via Google Container Engine (GKE), deploying to AWS, or pulling to local machines using the Docker command line interface.

Via this integration, we have enabled the following activities with GCR:

  • Pull private images stored on GCR to use as basis for a continuous integration (CI) run

  • Push an image to GCR resulting from a successful CI run (i.e. after building and testing a source code change)

  • Pull a private image stored on GCR to use as the base image for a Dockerfile build

Pushing an image to GCR is available on all plans at no additional cost. Pulling images from GCR is available to our $1/mo Startup plan customers with dedicated hosts.

Read More

Topics: Docker, continuous deployment (CD), containers, continuous integration (CI), Google Container Registry, Google Cloud Platform

Posted by Archana Verma

 

Each month, we feature a Shippable employee or customer on our blog. This month, we shine the spotlight on Ragesh Krishna, one of Shippable's early employees who heads our Bangalore office as VP engineering. You can reach out to Ragesh on Twitter or LinkedIn

ragesh_k1. When did you join Shippable and what's your role at the company?

I was here from the very beginning. In fact, even before the company was called Shippable! I'm currently VP of Engineering and I work out of the Bangalore office.

2. What do you think has been the most dramatic change in the tech industry over the past year?

Containers went from being a curiosity to a "must have". People argue that the technology behind it isn't new at all and has existed in one form or another from the days of Solaris. They're absolutely right, but it was never really as accessible as it is today and that makes a big difference.

Read More

Topics: Shippable updates

Posted by David Grimes

 

Your application has been chugging along nicely when suddenly it grinds to a halt, again! After debugging thousands of lines of code you finally found the one tiny piece that caused it, but you have to reinitialize your whole service to fix it. How can you avoid this painful process every time your application inevitably breaks? By smashing it into pieces, and then letting each piece do its own thing! Thus your monolithic application becomes a series of interchangeable and easily manageable microservices.

MicroService

Shippable is evolving constantly, and the newest improvement to our infrastructure is the introduction of microservices. Our API not only handled http calls, it processed the tasks itself, so we're moving the processing of tasks into microservices. Microservices are self-managed, self-contained units that monitor dependencies, listen to changes, and complete tasks delegated to it. In this way we can take out the parts and put in new ones without disturbing other services.

Read More

Topics: Docker, development process, containers, how-to, nodejs

Posted by Avi Cavale

 

Over the last couple of days, our service has not been as stable as expected and I want to sincerely apologize for this. I understand that Shippable is very critical for your CI/CD workflow and any service interruption is extremely frustrating.

WE SCREWED UP.

We have fixed the problem now, our service stability has improved tremendously, and we will take every precaution to make sure it does not happen again in future. 

In the interest of full transparency, here is what happened.

Since July 2014, we at Shippable made a decision to move toward a micro services based architecture. To live the world of continuous delivery, we made small incremental changes to almost all pieces of our architecture. 

Read More

Topics: Shippable updates

 magnatiles

Lately, several folks have asked us about our reasoning behind adding build numbers as the version tags for Docker Hub images. Briefly, our current flow is -

- Pull code from GitHub
- Pull image from Docker Hub (or build from a Dockerfile)
- Run CI in the container
- If CI passes and push to Docker Hub is configured in the yml or Project Settings, push image to Docker Hub with a version tag <image name>:<build number>

The question is - why don't we just tag the image with <image name>:latest? What is the value behind versioning images?

Read More

Topics: Docker, continuous deployment (CD), development process, containers, continuous integration (CI), devops