A few days ago, we woke up to the sad news that the Thoughtworks team had decided to shut down Snap CI in August. We have the greatest respect for Thoughtworks and their mission and want to convey our best wishes to the team for their next adventure.
If you're a current Snap CI customer, Shippable is a great fit as a replacement CI/CD platform. It is completely free to try us out and we are happy to offer help with migrating your CI configuration to Shippable. Please contact firstname.lastname@example.org for more information.
Please read CI/CD and DevOps expert Yegor Bugayengo's blog ranking of CI providers where he ranks Shippable as the top platform. Shippable is also ranked first among all hosted CI providers on Slant.co.
While these rankings focus on CI, Shippable also provides value beyond CI by offering a complete platform for DevOps workflows, including deploying a versioned package into a series of environments, release management, approval workflows, etc.
Keeping up our 2017 resolution, here's a summary of the new features released in January for Shippable's Continuous Integration and Delivery platform. In addition, get a sneak peek of what's coming in February.
Enhancements to Jacoco code coverage reports: You can now get individual file level detail, trend graphs for average line coverage and branch coverage for overall coverage results of the last ten runs and download the code coverage file in the .tar.gz format
Ever since we added Continuous Delivery pipelines to Shippable, one of the most common feature requests has been around support for deployment to the open source container orchestration platform from Google: Kubernetes. And we're excited to announce that we've added this last week! We already support Amazon ECS, Google Container Engine (GKE), Joyent Triton, and Docker Cloud/Datacenter and with Kubernetes added to this list, you can now automate deployments to any major Container Service using Shippable.
Modern companies today recognize that ensuring better quality releases that ship more frequently results in a competitive advantage if done right. For most, this means adopting DevOps and having complete automation of their Continuous Integration and Continuous Delivery pipelines. For others, it means building cloud native apps and benefiting from all the newer tech like Docker, microservices architecture, etc.
Regardless of the overall approach, experts agree that DevOps and CI/CD should be an integral part of your strategy. Yet, even though 73% organizations claim to have some level of DevOps processes in place, the number of organizations who do it well enough to be effective is miniscule. There is no single reason for this, but let's look at the five common reasons why organizations fail to adopt CI/CD effectively.
Continuous integration is a process where every code commit is immediately integrated into a common shared repository and built and tested automatically. The developer making the code change gets immediate feedback and can fix bugs easily since bugs are found immediately and can be tracked down to a specific commit.
Continuous Deployment is a process in which the code is packaged and deployed to a series of environments like Dev, Test, Beta, and ultimately to the live environment in Production. Automating the Continuous Deployment workflow involves many aspects like deployments, promotion through the series of environments with quality control, release management with approvals, etc.
Amazon provides a hosted Container Service for Docker called EC2 Container Service (ECS) as part of its container focused suite of services. Many of our customers seem to love the ECR (EC2 Container Registry) and ECS combination to store and run their applications. Amazon ECS can be accessed by going to your AWS Management Console, selecting EC2 Container Service from the list of Services.
In part I of this series, I demonstrated a simple scenario where we built and pushed a Docker image to ECR as part of the CI build workflow. In this blog post, I will show how you can set up deployment of the same sample application into Amazon ECS, In the last part of this series, I'll show how you can complete your Continuous Delivery pipeline with deployment into subsequent environments, promotion workflows between environments, and release management.
If you want to see an extended version of this scenario in action, attend our webinar in February by signing up below: