playground: copy a build cache containing std archives on each build

Following CL 432535, archive files for std are not included in GOROOT.
As a result, the playground had to recompile the relevant parts of std
on each build, causing it to time out during health checks.

Try to fix this by copying a minimal amount of GOCACHE content for each
build, rather than recompiling. Use hard linking to avoid copying bytes.

For golang/go#57495

Change-Id: I06bf9f2630d1f9e4675847586911b45054d05222
Reviewed-on: https://go-review.googlesource.com/c/playground/+/460635
Reviewed-by: Heschi Kreinick <heschi@google.com>
Run-TryBot: Robert Findley <rfindley@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Bryan Mills <bcmills@google.com>
2 files changed
tree: 47d2d6858211c1df002fbad79752850820d03073
  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. cache.go
  13. client.go
  14. codereview.cfg
  15. CONTRIBUTING.md
  16. Dockerfile
  17. edit.go
  18. edit.html
  19. enable-fake-time.patch
  20. examples.go
  21. fake_fs.lst
  22. fmt.go
  23. fmt_test.go
  24. go.mod
  25. go.sum
  26. LICENSE
  27. logger.go
  28. main.go
  29. Makefile
  30. metrics.go
  31. PATENTS
  32. play.go
  33. play_test.go
  34. README.md
  35. sandbox.go
  36. sandbox_test.go
  37. server.go
  38. server_test.go
  39. share.go
  40. store.go
  41. tests.go
  42. txtar.go
  43. txtar_test.go
  44. version.go
  45. 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-triggers and pull-cloudbuild-triggers 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.