Skip to content

GitHub Actions test for composer based WP in Pantheon

Notifications You must be signed in to change notification settings

wpugph/gh-action1

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

116 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Visual Regression Testing Sample deployment code

This sample code uses:

WorkFlow:

  • Code pushed to GitHub
  • GitHub Actions kicks in to do the composer install, core, theme and plugin updates
  • Deploy latest code to development site
  • Do Visual Regression to the Development site VS Live site
  • Deploy the backstop reports to a QA multidev in Pantheon

Setup Pre-requisite fo youn to use this build:

You'll need an account in Pantheon and in GitHub to test this build

  1. Github account for repo and CI/CD ( You can use GitLab or Bitbucket but you may need to modify to match their variables )
  2. Pantheon account for Hosting ( You can use other hosting but you'll have to modify the script accordingly)

Setup:

  1. Clone this repo
  2. Modify .github/workflows/composer-build.yml to reflect your

REFERENCE_SITE_URL

QA_PANTHEONENV

PANTHEONENV

PANTHEONSITENAME

  1. Further modify scripts/github/test/backstopjs/backstopConfig.js for additional settings

  2. Add these as secret tokens in GitHub

PANTHEONEMAIL - Your Pantheon registered email

PANTHEONSITEUUID - Site UUID where your code will be deployed to

STAGING_PRIVATE_KEY - https://pantheon.io/docs/ssh-keys

MACHINETOKEN - https://pantheon.io/docs/machine-tokens#create-a-machine-token

Why we use composer in WP?

  • Easier plugin, theme and core version management from composer.json file
  • Less merge conflicts
  • Only maintain build scripts and custom code in the repo
  • Easier for team members to replicate setup

About

GitHub Actions test for composer based WP in Pantheon

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •