We are excited to announce the release of significant enhancements to Shippable Continuous Integration and the introduction of a new product, Shippable Formations. Together, these two products transcend traditional DevOps and take it to the next level, to DevOps 2.0.
DEPRECATED BLOG:
We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.
We are very excited to announce the release of our new product line, Shippable Formations. Along with Shippable CI/CD, this is the first step in our journey towards enabling DevOps 2.0 - frictionless Dockerized pipelines from code to production without the need for any DevOps code or scripts.
Over the last several months, we've received a lot of feedback on our Shippable CI/CD product. One thing resonated above all - as customers start adopting Docker-based workflows and creating complex, multi-container applications, they were looking for something beyond CI/CD. Most of them were creating these workflows themselves, and this was taking valuable time away from what they really wanted to do, namely work on their product.
As early adopters of Docker, we had created many internal workflows and processes that helped us ship faster. Shippable Formations is the productized version of all that we've learnt from shipping to production 5x-20x a day.
Have you ever wasted your time debugging a broken build only to realize a few frustrated hours later that it was due to something that changed in one of the images you depend on?
Lighthouse to your rescue!
Lighthouse is available to all Shippable users for free! Using this feature, you can 'watch' any public Docker image or any private image you have access to from any registry and get notified via email when that image is updated.
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?
This week, the Shippable team had the opportunity to present 'Modern DevOps with Docker' (describing our internal transformation - see below for more) and engage with the community at ApacheCon 2015 in Austin, TX. We saw firsthand how the thriving group of dedicated professionals in the Apache community are tackling big challenges across the full tech spectrum. In addition, while in Austin, we had the chance to connect with the tight-knit and talented DevOps Austin community and learn from their perspectives. It was an energizing three days.
