Skip to content

Stepped Release on to Public Sites

Richard Wallis edited this page Oct 28, 2016 · 2 revisions

To put a new release on to a public site (webschemas.org, schema.org). We need to load a new labeled version onto the site, exercise the site to get the caching loaded, then divert traffic to that new loaded version.

Step 1. Label version

In the relevant .yaml files (webschemas.yaml, schemaorg.yaml) set the version value. eg. version: 3-2 for version 3.2

Step 2. Deploy application.

eg. appcfg.py update webschemas.yaml -A webschemas-g

Step 3. Identify the Site

Identify the site as defined in appengine, NOT its public facing domain name.

eg. webschemas-g.appspot.com is the appengine view of the webschemas.org site.

Step 4. Exercise the Site

Run the exercise script passing the site url, prefixed with the version, as argument to the script.

eg. scripts/exercisesite.py -s http://3-2.webschemas-g.appspot.com

Sit back and watch for a few minutes - it will take time to speed up as the caches are loaded.

Set New Version as Serving Normal Access

In the Appengine Console. Select versions listing. Select new version then Migrate Traffic option.