Google Git
Sign in
go / playground / refs/heads/dev.go2go
commit6aa43c4150244e736b00db698eb6ce75ba2a29aa[log] [tgz]
authorHeschi Kreinick <heschi@google.com>Fri Jun 11 16:28:15 2021 -0400
committerHeschi Kreinick <heschi@google.com>Mon Jun 14 16:54:08 2021 +0000
tree8ec16730ac6afb04e6221efa4dc2bfe5e9c726c8
parentfb5cd7c02be838e9cfa75af8734bddd9f022741f [diff]
[dev.go2go] deploy: use gcloud to manage triggers, trigger from GCR

The GCP UI is nicer for editing triggers, and the gcloud command now has
beta support for import/export. It wants YAML format, though. Delete the
json versions and replace them with freshly pulled versions, including
the change to trigger from GCR.

Change-Id: If05944fdd6cca6d7f72b56ade191a3b00c333b9e
Reviewed-on: https://go-review.googlesource.com/c/playground/+/327389
Trust: Heschi Kreinick <heschi@google.com>
Run-TryBot: Heschi Kreinick <heschi@google.com>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Alexander Rakoczy <alex@golang.org>
6 files changed
tree: 8ec16730ac6afb04e6221efa4dc2bfe5e9c726c8
  1. cmd/
  2. deploy/
  3. examples/
  4. internal/
  5. sandbox/
  6. static/
  7. .gitignore
  8. app.yaml
  9. AUTHORS
  10. cache.go
  11. client.go
  12. codereview.cfg
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. Dockerfile
  16. edit.go
  17. edit.html
  18. enable-fake-time.patch
  19. fake_fs.lst
  20. fmt.go
  21. fmt_test.go
  22. go.mod
  23. go.sum
  24. LICENSE
  25. logger.go
  26. main.go
  27. Makefile
  28. PATENTS
  29. play.go
  30. play_test.go
  31. README.md
  32. sandbox.go
  33. sandbox_test.go
  34. server.go
  35. server_test.go
  36. share.go
  37. store.go
  38. tests.go
  39. txtar.go
  40. txtar_test.go
  41. vet.go
README.md

playground

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

Building

# build the image
docker build -t 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

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 builds submit --config deploy/deploy.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-go2go:latest gcr.io/golang-org/playground-go2go:latest
docker push gcr.io/golang-org/playground-go2go:latest
gcloud --project=golang-org --account=you@google.com app deploy app.yaml --image-url=gcr.io/golang-org/playground-go2go: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.