Create Multiple Builds from the Same Source Using Different AWS CodeBuild Build Specification Files

Wed, 02 Aug 2017 04:40:10 +0000

In June 2017, AWS CodeBuild announced you can now specify an alternate build specification file name or location in an AWS CodeBuild project.

In this post, I’ll show you how to use different build specification files in the same repository to create different builds. You’ll find the source code for this post in the GitHub repo.

Requirements

The AWS CLI must be installed and configured.

Solution Overview

I have created a C program (cbsamplelib.c) that will be used to create a shared library and another utility program (cbsampleutil.c) to use that library. I’ll use a Makefile to compile these files.

Continuous Delivery of Nested AWS CloudFormation Stacks Using AWS CodePipeline

Wed, 28 Jun 2017 08:45:47 +0000

In CodePipeline Update – Build Continuous Delivery Workflows for CloudFormation Stacks, Jeff Barr discusses infrastructure as code and how to use AWS CodePipeline for continuous delivery. In this blog post, I discuss the continuous delivery of nested CloudFormation stacks using AWS CodePipeline, with AWS CodeCommit as the source repository and AWS CodeBuild as a build and testing tool. I deploy the stacks using CloudFormation change sets following a manual approval process.

Here’s how to do it:

In AWS CodePipeline, create a pipeline with four stages:

DevOps on Technology Enlightened

Create Multiple Builds from the Same Source Using Different AWS CodeBuild Build Specification Files

Continuous Delivery of Nested AWS CloudFormation Stacks Using AWS CodePipeline