deploy: use more powerful instance for deploy

Deploy takes a ridiculous amount of time because it is
building toolchains and so on. Give it some actual CPU.

Change-Id: Id02b2d0de66b88066d0e1e83b8e1477b3dcd0cae
Reviewed-on: https://go-review.googlesource.com/c/playground/+/375634
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
2 files changed
tree: 074a464668f728b4163b9362d1d0fe95883387f1
  1. cmd/
  2. deploy/
  3. examples/
  4. internal/
  5. sandbox/
  6. static/
  7. .gitignore
  8. app.go2go.yaml
  9. app.goprev.yaml
  10. app.gotip.yaml
  11. app.yaml
  12. AUTHORS
  13. cache.go
  14. client.go
  15. codereview.cfg
  16. CONTRIBUTING.md
  17. CONTRIBUTORS
  18. Dockerfile
  19. edit.go
  20. edit.html
  21. enable-fake-time.patch
  22. examples.go
  23. fake_fs.lst
  24. fmt.go
  25. fmt_test.go
  26. go.mod
  27. go.sum
  28. LICENSE
  29. logger.go
  30. main.go
  31. Makefile
  32. metrics.go
  33. PATENTS
  34. play.go
  35. play_test.go
  36. README.md
  37. sandbox.go
  38. sandbox_test.go
  39. server.go
  40. server_test.go
  41. share.go
  42. store.go
  43. tests.go
  44. txtar.go
  45. txtar_test.go
  46. version.go
  47. vet.go
README.md

playground

Go Reference

This subrepository holds the source for the Go playground: https://play.golang.org/

Building

# build the image
docker build -t golang/playground .

Running

docker run --name=play --rm -p 8080:8080 golang/playground &
# run some Go code
cat /path/to/code.go | go run client.go | curl -s --upload-file - localhost:8080/compile

To run the “gotip” version of the playground, set GOTIP=true in your environment (via -e GOTIP=true if using docker run).

Deployment

Deployment Triggers

Playground releases automatically triggered when new Go repository tags are pushed to GitHub, or when master is pushed on the playground repository.

For details, see deploy/go_trigger.yaml, deploy/playground_trigger.yaml, and deploy/deploy.json.

Changes to the trigger configuration can be made to the YAML files, or in the GCP UI, which should be kept in sync using the push-cloudbuild-trigger and pull-cloudbuild-trigger make targets.

Deploy via Cloud Build

The Cloud Build configuration will always build and deploy with the latest supported release of Go.

gcloud --project=golang-org builds submit --config deploy/deploy.json .

To deploy the “Go tip” version of the playground, which uses the latest development build, use deploy_gotip.json instead:

gcloud --project=golang-org builds submit --config deploy/deploy_gotip.json .

Deploy via gcloud app deploy

Building the playground Docker container takes more than the default 10 minute time limit of cloud build, so increase its timeout first (note, app/cloud_build_timeout is a global configuration value):

gcloud config set app/cloud_build_timeout 1200  # 20 mins

Alternatively, to avoid Cloud Build and build locally:

make docker
docker tag golang/playground:latest gcr.io/golang-org/playground:latest
docker push gcr.io/golang-org/playground:latest
gcloud --project=golang-org --account=you@google.com app deploy app.yaml --image-url=gcr.io/golang-org/playground:latest

Then:

gcloud --project=golang-org --account=you@google.com app deploy app.yaml

Contributing

To submit changes to this repository, see https://golang.org/doc/contribute.html.