The CI/CD and DevOps Blog

Learn about various tried-and-tested strategies that will help you ship code faster

CI/CD new features: Kubernetes, JaCoCo, and more

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.

Continuous Integration

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

 

CI/CD enhancements: JaCoCo, JFrog Artifactory, and more

Happy 2017! As the new year kicks in, we wanted to start a monthly blog that lets you know the new features we've launched in the last month. No more trees (aka features) falling silently in the forest... they'll make a big THUDDDDD in this monthly series. So without further ado.... TA DA!

Continuous Integration

Custom variables for manual builds: You can now inject custom environment variables while triggering a manual build through the UI. This is great while debugging when you don't want to make fake commits just to trigger builds with different env values. 

Integrated JaCoCo code coverage reportsYou can visualize rich reports within the Shippable UI and drill down to see which llnes of code are not covered by your tests. 

While Containers Move to the Mainstream, Some Roadblocks Exist on Path to Adoption

Developers are increasing their use of containers for new applications, but a technology skills gap is impeding widespread adoption of container technology. These are two of the key findings of our latest survey on container adoption among developers. Shippable worked with independent research firm Survata to survey of 300 developers about their current and expected use of container technologies. The results were interesting in a number of ways.

undefined-864167-edited.jpg

Docker applications with Google Container Registry and Shippable

     

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

The above options are available on all Shippable plans at no additional charge.