- Pantheon drupal update#
- Pantheon drupal code#
Backups of sites with large a large database or media files are taking too long and timing out on Circle CI (10 mins). LIVE_URL: The preferred custom domain (full URL) for the live environment to use in visual regression testing or set to 0 to use the live-SITE_NAME Pantheon hosted URL,. RECREATE_MULTIDEV: 0 or 1 to determine if the multidev is deleted and recreated. 
You may want to disable for sites where a backup takes longer than 10 minutes and you have regularly backups scheduled via another method.
CREATE_BACKUPS: 0 or 1 to determine if a backup of the live site is made before deployment. SITE_NAME: The site machine name, which can be acquired with terminus site:list. SITE_UUID: The site UUID, which can be acquired with terminus site:list or is in the dashboard URL for the site. The order is important do not change the order of the keys in the object or skip keys. Edit sites-to-auto-update.json and set the following key for each JSON object for sites you wish to auto update. Add an (public) SSH key to Pantheon and (the private key) to the CircleCI project. SITE_NAME: The Pantheon site name if not provided via sites-to-auto-update.json. SITE_UUID: The Pantheon site UUID if not provided via sites-to-auto-update.json. SLACK_USERNAME: The username to post to Slack with. SLACK_CHANNEL: The Slack channel to post notifications to. SLACK_HOOK_URL: The Slack incoming webhook URL. TERMINUS_MACHINE_TOKEN: A Pantheon Terminus machine token with access to the org above. CIRCLE_TOKEN: A Circle CI API token with access to the project created in step 3. MULTIDEV: The multidev name to use for applying/testing updates. Add environment variables to CircleCI for the following:. Pantheon drupal update#
Update to meet your needs, tweaking things like viewport. Pantheon drupal code#
Don't fork this repository, instead clone it and change the remote URL to your own fresh GitHub repository and push the code there. Deploy the test environment to the live environment. This is opt-out per site and should only be disabled if backups take longer than 10 minutes and you have regularly backups scheduled via another method. Create a backup of the test environment. Deploy the dev environment to the test environment. Merge the multidev environment with the dev environment. If the visual regression test fails the script will stop here and post a link to the visual regression report in Slack. Use BackstopJS to run a visual regression test between the live environment and the multidev environment. If no Drupal updates are available the script will stop here. Check for and apply Drupal theme updates via Drush, if available. Check for and apply Drupal module updates via Drush, if available. Switch the multidev environment update-dr to SFTP mode. Custom upstream updates will be applied if using a custom upstream. Drupal core updates are managed in the default upstream. Check for and apply Pantheon upstream updates. Switch the multidev environment update-dr to git mode. This is opt-out per site and should only be disabled if using Solr or multidev creation takes more than 10 minutes. Deletion and recreation is done to clear any existing changes and pull the latest database/files from the live environment. Recreate the multidev environment update-dr. Delete the multidev environment update-dr. 
Authenticate with Terminus via machine token. This script will loop through all sites in sites-to-auto-update.json and: Scalable automated testing and deployment of upstream (Drupal 7 core), module and theme updates on Pantheon sites with help from Terminus, CircleCI, Drush, BackstopJS and Slack. 
Pantheon Drupal 7 Auto Update Description
0 kommentar(er)
