The Shippable 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!

What is Modern Application Delivery?

Development practices have come a long way since the time of Waterfall. Development shops have progressed through Agile methodologies and have built a culture of continuously delivering value to their customers, both internally and externally. Many shops have also since implemented Scrum and are experimenting with containerization technologies.

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.

Five common mistakes while setting up Continuous Integration and how to avoid them

Since the latest release of our platform, I have been reviewing the customer experience to make sure customers find it easy to onboard and get to a green build for their projects. After analyzing the problems customers run into, I noticed five situations that are fairly common. I want to share these and ways to avoid them so you can get up and running as quickly as possible. 

End-to-end container pipelines with Amazon EC2 Container Registry now available

We have significantly updated the Shippable platform with several new features. Hence this blog post is deprecated.

Check out our blog - Deploy your first Continuous Deployment Pipeline, that uses Docker Hub for image registry and Amazon EC2 Container Service (ECS) for container service.

For the latest information, refer our documentation, and/or open a support issue, if you have questions.

If you've thought about running containers on AWS, today's a big day.  With the introduction of Amazon EC2 Container Registry today, you can now establish and run a container-based pipeline entirely within AWS.  And with Shippable, setting up and running that pipeline with full visibility, history and control has never been easier.

During AWS re:Invent 2015, we announced our preview release for integration between Shippable and Amazon EC2 Container Service (Amazon ECS).  Today, we're thrilled to announce that we've added integration with Amazon EC2 Container Registry (Amazon ECR), as well. With this integration, Shippable customers can now pull and push Docker images from Amazon ECR as part of their Shippable CI builds and deploy them with Shippable Formations across multiple clusters in Amazon ECS, without ever having to manually update a Task Definition yourself.  Shippable automatically updates your ECS task definitions with the latest image information based on your CI builds and either automatically deploys or deploys with a single-click when you're ready.