Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You could send a small % of users to the new version as detailed here: <a href="https://developers.google.com/appengine/docs/adminconsole/trafficsplitting" rel="nofollow">https://developers.google.com/appengine/docs/adminconsole/trafficsplitting</a></p> <blockquote> <p>App Engine's Traffic Splitting tool allows you to roll out features for your app slowly over a period of time, similar to what Google does when rolling out a new feature over a few days or weeks. Traffic Splitting also allows you to do A/B Testing. Traffic Splitting works by splitting incoming requests to different versions of your app.</p> <p>To set up Traffic Splitting, choose a non-default version of your app with code you want to test, specify the percentage of traffic it should receive, and choose the type of splitting to use. It also important to pay attention to the effects of caching on the static and dynamic resources in your app.</p> </blockquote> <p>You also have options regarding routing:</p> <blockquote> <p>Each request arriving at an app is sent to a particular version of the app. Normally, the versions are distinguished by URL. For example, consider an app called codeninja with three active major versions: alpha, beta, and default. All traffic sent to <a href="http://codeninja.appspot.com" rel="nofollow">http://codeninja.appspot.com</a> goes to the default version, but you can send traffic to other versions by including their version name as a prefix (for example, you could access the beta version of the codeninja app via <a href="http://beta.codeninja.appspot.com" rel="nofollow">http://beta.codeninja.appspot.com</a>.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload