Skip to content

Latest commit

 

History

History
60 lines (31 loc) · 1.94 KB

deploying.md

File metadata and controls

60 lines (31 loc) · 1.94 KB
Raw

Deploying

Integration

This happens automatically as a post build action when the govuk_smart_answers master build passes on CI.

Manually

You can use the Integration Deploy App. Click the "Build with Parameters" link and enter "release" as the "TAG".

Production

These are usually done with a Smart Answers developer sitting with someone from 2nd-line Support. You need to prepare a production deployment as follows:

Create the Release in GitHub

1. Find the latest release

Open the list of releases and make a note of the name of the most recent release (referred to as $RELEASE-TAG below).

NOTE. Jenkins and releases

After a successful build of the master branch on Jenkins:

  • Jenkins updates the release branch to point at HEAD
  • Jenkins creates a release_nnnn tag pointing at HEAD

2. Review the changes waiting to be deployed to production

Open "https://github.com/alphagov/smart-answers/compare/deployed-to-production...$RELEASE-TAG".

Open each of the merged Pull Requests that are waiting to be deployed and ensure that the description contains details of the expected changes.

3. Update the latest release on GitHub

Open "https://github.com/alphagov/smart-answers/releases/tag/$RELEASE-TAG".

Click "Edit release".

Leave the "Release title" blank.

Set the description to:

## All included PRs

TODO: List each of the Pull Requests included in the release, for example:

* PR https://github.com/alphagov/smart-answers/pull/nnn - <title-of-pull-request>

## PRs to check post-deployment

TODO: List each of the Pull Requests that contain user facing changes here, for example:

* PR https://github.com/alphagov/smart-answers/pull/nnn - <title-of-pull-request>