Skip to content
This repository was archived by the owner on Mar 24, 2021. It is now read-only.

Transactions Explorer

Jump to bottom
Alex Muller edited this page Aug 19, 2013 · 1 revision

Deployment

Like any good GDS app, Transactions Explorer is deployed using Jenkins.

Building the tarball

On deploy.preview.performance, run the job transactions-explorer-build-artefact with the parameter (tag) you want to use. This will build a preview and production tarball, and trigger a downstream job to update preview using GOV.UK's deploy.preview.

This build job is also triggered by a successful Jenkins build of transactions-explorer (which results in an updated git release tag). Preview is therefore kept up to date by successful builds from master.

Note: the Transactions Explorer build requires a version of Python which is unavailable on GOV.UK CI infrastructure.

Deploying to staging and production

Build the tarball that you want to want to deploy using the above job, with a specific release tag like release-404. Use GOV.UK's deploy.staging and deploy.production and run the deploy jobs for Transactions Explorer with the artefact ID (build number) you just built as a parameter.

Example:

  1. Run transactions-explorer-build-artefact on deploy.preview.performance with a git tag as a parameter: release-444.
  2. Make sure preview looks nice.
  3. Run the Transactions Explorer deploy task on deploy.staging with the build number that Jenkins returned you from step 1 (e.g. 123).
  4. Make sure staging looks nice.
  5. Repeat steps 3 and 4 with s/staging/production/g.

Clone this wiki locally