Table of contents

This is for internal use by the PaaS team. Public-facing documentation is located at docs.cloud.service.gov.uk.

ADR013: Building BOSH releases

Context

We use Bosh to create and manage our cloudfoundry deployment on AWS. To deploy software, Bosh needs certain binary dependencies available. These are known as bosh releases.

Before this decision, we usually built and uploaded releases to Bosh as part of our concourse pipeline. Occasionally, we would manually build a release, store it on GitHub, and point Bosh to it there.

Building Bosh Releases

We investigated different approaches to creating bosh releases, in particular

The work on these spikes was recorded in https://www.pivotaltracker.com/n/projects/1275640/stories/115142265 https://www.pivotaltracker.com/n/projects/1275640/stories/128937731

Decision

We will use the pullrequest-resource approach to build all our Bosh releases in a consistent way.

Status

Accepted

Consequences

We must gradually migrate all our Bosh release builds to their own build pipelines. We will need separate jobs to build from master - this already has a proof of concept in the spike. We may have to add additional config in projects we fork to allow us to create final builds.