Skip to content

Pantheon WebOps Workflow

Code moves up, content moves down
Code moves up, content moves down

Please read this high level Pantheon documentation page, to get a basic understanding of the workflow.

Environment Descriptions

Multidev

An individual development environment that is technically a git branch. These can be used for features, fixes, or individual developers to have an environment.

Dev

This is the master branch. Multidevs will get merged and deployed to Dev. The database is frequently overwritten, so don't depend on CMS DB changes to persist.

Test

The final environment stop before Live. This environment is very similar to Dev but with one key difference, it has traffic routing through the AGCDN layer. The AGCDN provides the following features:

  • Injects an HTTP header with the ISO2 country code of the origin of the request (cf-ipcountry)
  • Web Application Firewall
  • Edge redirects
  • On the fly image optimization

Live

The Live, production environment. Unlike the lower environments, we do not overwrite this database and changes can be expected to persist.

After The Site Has Launched

Once your site has launched, there are a few more rules and procedures to follow for pushing out new code. These need to be followed to keep everybody sane and things to happen smoothly.

Wordpress Core and Plugin Updates

We make use of an automated update tool from Pantheon called Autopilot. This tool periodically checks for updates, creates a multidev, applies the updates, performs visual regression testing, and deploys to the Live environment.

Process to Deploy Code

  1. Dev work happens in a multi-dev and the fix/feature is validated and approved by Brown-Forman stakeholders on that environment.
  2. Upon approval and a fix/feature is ready to go live, merge that Multidev into Dev and refresh the db/files from Live. This should be a good test of the deployment.
  3. Test the fix/feature on Dev to be sure you are seeing the expected behavior
  4. Inform your Brown-Forman contact that the fix/feature is approved, deployed to dev, and tested. When contacting us, please provide the following:
    • Which site are you working on? (We're a small team that manages a lot of sites, details prevent mistakes)
    • Quick summary of the fix/feature
    • Any additional steps needed to complete the deployment other than pushing files
      • Example: Log into the dashboard and run the ACF JSON sync on the Foo field group
    • Is there a specific deadline to get this fix/feature deployed?
  5. Someone from Brown-Forman IT will deploy the code to the Test environment, sync the db/files from Live to Test, and perform any additional steps you provided.
  6. We will inform you when the push has been completed to Test and request that you verify that everything is working as intended.
  7. When the Test environment has been verified, we will backup Live, and repeat the process to push to Live.
  8. Once the fix/feature is live, we'll request one final check that everything is working as expected.