I recently had someone ask whether Shippable supports testing their builds against multiple minor Java versions. The answer is "YES!" and in this blog I'll share two ways to do it and walk through an example setup.
Yesterday, I attended Container Summit: The Future of Containers in the Enterprise, which occurred in cooperation with the Interop conference. Thanks to the great people at Joyent, it was a day packed with fantastic presentations and more than a few takeaways.
My über takeaway from the day is that it's getting harder and harder to talk about containers without also talking about microservices. There were examples of containers in use for a variety of use cases, but it was their particular suitability for use with microservices that came through loud and clear.
In addition to that uber takeaway, here were my top five takeaways from the summit:
- Microservices are the next big tech wave
- Microservices create complexity
- Developer experience and developer velocity are key success factors
- There likely won't be one winner for container orchestration
- Running containers on bare metal isn't just for the brave
And check below for my favorite one-liner from the event :)
This post will be the first in a series of posts covering the basics of using Terraform to configure a container cluster on AWS and run a service on the cluster. If you're not already familiar, Terraform is a pretty incredible open source tool from Hashicorp for configuring and launching infrastructure across a variety of providers. By enabling you to manage your infrastructure provisioning and configuration as code (i.e. "Infrastructure as Code"), Terraform gives you repeatability and consistency, which you'll find tremendously useful when setting up complicated infrastructures, such as a container cluster and its underlying infrastructure on AWS.
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.
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.
We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. Checkout a similar blog of deploying your first Continuous Deployment pipeline using Docker Hub and Amazon EC2 Container Service. For the latest information, refer to our documentation and/or open a support issue, if you have questions.
Today's a big day! We're thrilled to announce the integration of our Shippable CI/CD platform with Amazon EC2 Container Service (ECS) and the coming integration with Amazon EC2 Container Registry (ECR). With this integration, Shippable customers can easily deploy the Docker images generated from their Shippable CI processes into Amazon's services for managing and running containers.