Table of contents

Deploy an application to GOV.UK

Teams are responsible for deploying their own work. We believe that regular releases minimise the risk of major problems and improve recovery time. The 2nd line team is responsible for providing access to deploy software for teams who can’t deploy it themselves.

If you are responding to a security incident, follow the steps to deploy fixes for a security vulnerability.

1. Test on integration

Code that is merged to master is automatically deployed to integration. You should verify that your changes work there.

2. Check the context

The golden rule is that you only deploy what you can support.

  • This means that deploys generally take place between 10am and 4pm, the core hours when most people are in the office.
  • Check #govuk-deploy recent history and the channel topic. In some circumstances we may institute short deployment freezes, they will be announced in that channel.
  • Announce your deployment in #2ndline if it’s potentially problematic.

3. Check your changes

Go to the Release application and find the application you want to deploy. Then select the release tag you want to deploy.

  • Check what you will be deploying. If there’s other people’s code to deploy, ask them whether they’re okay for the changes to go out.
  • Check if there’s a deploy note for the application, to see if there are any special instructions or reasons not to deploy.

4. Deploy to staging

From the Release application, click the deploy buttons. If you have production access, this will bring you to the Jenkins job to deploy your change.

Once deployed to staging, you will need to:

5. Deploy to production

Again:

Stay around for a while just in case something goes wrong.

This page was last reviewed . It needs to be reviewed again by the page owner #govuk-2ndline.