The CI/CD and DevOps Blog

Do more with less - No one disagrees with this famous quote, but how often do we really take a step back to think about pushing the envelope with what we have right now ? At Shippable, we've tried to constantly ask this question with every feature we've built. This ideology manifests itself in the capabilities the current Shippable workflows have, compared to what they used to a few years back. All this while keeping things simple and with zero additional costs to the customers. A lot of our customers started using Assembly Lines after the launch, a year go. Most of them didn't need much help but we do admit that some steps in extending traditional CI with the new Assembly Lines are a bit complicated. The objective of this post is to provide a detailed, step by step guide, to enable any CI job on Shippable to use the power of Assembly Lines.  

We are excited to announce native support for hosted CI/CD on Armv8-A architecture! This launch is a result of a close partnership with Arm and Packet to give Arm developers quick and easy access to native test infrastructure, enabling them to significantly improve productivity and reliability with fast builds and identification of bugs earlier in the development process.

In the absence of readily available CI/CD services that natively supports Arm, developers relied on emulators while building and validating their code, which does not always detect architecture specific artifacts being introduced in their codebases. As the adoption of the Armv8-A architecture continues to grow, it is critical for organizations to have easy access to a CI/CD platform that natively supports Arm and doesn’t require resources and effort to set up and manage. Today's announcement addresses this need with a solution that offers hosted build and test infrastructure with no installation or management overhead.

This announcement would not have been possible without tremendous contributions from Packet and Arm. The Armv8-a machines are hosted on Packet's cloud and the Arm team has been key in driving this effort to fruition. Read the entire text of the announcement here. 

This tutorial explains how to manually create a GCE VM image using Packer. Before you start, you should be familiar with the following concepts:

• GCE Virtual Machines
• GCE Images
• Packer Intro
• Google Compute Builder
• Shell Provisioner

The best way to get started is to install Packer and run scripts manually on your local machine to create a VM image. Once you understand the mechanics of it, you should consider automating your workflow by following our documentation on Automated creation of GCE image using Packer.

This tutorial explains how to build an AWS AMI using Packer. Before you start, you should be familiar with the following concepts:

• Packer Intro
• Amazon Instance Builder
• File Provisioner
• Manifest Post Processor

The best way to get started is to install Packer and run scripts manually on your local machine to create an AMI. Once you understand the mechanics of it, you should consider automating your workflow by following our documentation on Automated AWS AMI creation using Packer.

This tutorial explains how to manually provision an AWS EC2 virtual machine using Terraform. Before you start, you should be familiar with the following concepts:

• AWS EC2
• Terraform overview
• Terraform aws_instance
  
  

The best way to get started is to install Terraform and run scripts manually on your local machine to provision a VM. Once you understand the mechanics of it, you should consider automating your workflow by following our documentation on Automated provisioning of AWS EC2 using Terraform.