blog, go.dev, tour: update deployment instructions

Automatic deployment is now enabled for these web sites.
(But not yet for golang.org. Waiting on the pending CLs for
better testing.)

Change-Id: I19a690d6354f83601be355b1eb5ca8003efd911a
Reviewed-on: https://go-review.googlesource.com/c/website/+/324410
Trust: Russ Cox <[email protected]>
Run-TryBot: Russ Cox <[email protected]>
Website-Publish: Russ Cox <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>

Author: rsc

blog/README.md

@@ -43,27 +43,10 @@ subject line, so it is easy to find.
 
 ## Deploying
 
-The Google Cloud project triggers a fresh deploy of the blog on each submit
-but that deployment is published to a temporary URL.
+Each time a CL is reviewed and submitted, the blog is automatically redeployed to
+https://blog.golang.org/.
 
-To publish the blog to blog.golang.org, you need access to the
-Cloud Console for the golang-org project.
-Then:
+If the automatic redeploy is not working, or to check on the status of a redeploy,
+see the “website-redeploy-blog” trigger in the
+[Cloud Build console](https://console.cloud.google.com/cloud-build/builds?project=golang-org).
 
-1. Visit the
-   [builds list](https://console.cloud.google.com/cloud-build/builds?project=golang-org&query=trigger_id%3D%22c99674d3-32c1-4aec-ade4-ae2d5a844369%22)
-   and click on the build hash for the most recent build
-   with trigger name “Redeploy-blog-on-blog-commit”.
-
-   Scrolling to the bottom of the build log, you will find a URL in a log message like
-
-       Deployed service [blog] to [https://TEMPORARYURL.appspot.com]
-
-2. Copy that URL and load it in your browser. Check that it looks OK.
-
-3. Assuming it does, visit the
-   [AppEngine versions list](https://console.cloud.google.com/appengine/versions?project=golang-org&serviceId=blog).
-   Click “Migrate Traffic” on the new entry to move 100% of the blog.golang.org
-   traffic to the new version.
-
-4. You're done.

go.dev/README.md

@@ -13,12 +13,12 @@ To serve the go.dev pages, run
 
 ## Deploying
 
-All commits pushed to `master` will be automatically deployed to https://go.dev.
+Each time a CL is reviewed and submitted, the web site is automatically redeployed to
+https://go.dev/.
 
-For now moment, the deployment is not automatic. Instead, after submitting,
-visit the [Cloud Build triggers list](https://console.cloud.google.com/cloud-build/triggers?project=go-discovery),
-find the one named “Redeploy-go-dev-on-website-commit”, which should say “Disabled” in the status column,
-and then click “RUN”.
+If the automatic redeploy is not working, or to check on the status of a redeploy,
+see the “website-redeploy-go-dev” trigger in the
+[Cloud Build console](https://console.cloud.google.com/cloud-build/builds?project=golang-org).
 
 ## Commands
 

tour/README.md

@@ -43,21 +43,13 @@ at https://github.com/golang/tour/issues.
 
 ## Deploying
 
-1.	To deploy tour.golang.org, run:
+Each time a CL is reviewed and submitted, the tour is automatically redeployed to
+https://tour.golang.org/.
 
-	```
-	GO111MODULE=on gcloud --project=golang-org app deploy --no-promote app.yaml
-	```
+If the automatic redeploy is not working, or to check on the status of a redeploy,
+see the “website-redeploy-tour” trigger in the
+[Cloud Build console](https://console.cloud.google.com/cloud-build/builds?project=golang-org).
 
-	This will create a new version, which can be viewed within the
-	[golang-org GCP project](https://console.cloud.google.com/appengine/versions?project=golang-org&serviceId=tour).
-
-2.	Check that the deployed version looks OK (click the version link in GCP).
-
-3.	If all is well, click "Migrate Traffic" to move 100% of the tour.golang.org
-	traffic to the new version.
-
-4.	You're done.
 
 ## License