Pushing a Specific Build of a Book

Using the CLI

Follow the instruction below to push a specific builds using a combination of data from the Concourse ATC and the CLI:

1. On Concourse, visit the specific successful staging build that you want to use for production.
2. At the bottom of the build page, open the push to staging console.
3. Search for 'Green build', which will be at the bottom of the page. You will see a line such as Green build #20151023_1744 has been uploaded to S3 for docs-book-pivotalcf.
4. Copy the build identifier from the above line. In this example, the build identifier is 20151023_1744.
5. In your terminal, in the directory of the book that you want to push to production, run this command: bundle exec bookbinder push_to_prod <build-identifier>

Note: We could potentially improve this interface by allowing users to specify the Concourse staging build number instead of the timestamp. To do this, we'd access the required information through an API call, using the Checkman Concourse script as an example.

Using Concourse

We also think we could set up our S3 bucket as a Concourse resource that we then feed into the production job.

To push past versions, you would do the following

1. Visit the resource page of the S3 bucket by clicking its name (i.e. resource page for the docs-mysql resource), and finding the version of the resource you want pushed to production.
2. From the top down, click the power button icons for the refs until you've reached the version you want - this toggles which ones are being used.
3. We would then use the most recent version of the resource that is marked as green for the production job.

When you toggle the resource versions, these changes persist.