gotipplay: identify the gotip playground build in the UI

Attempt to clearly label the Go tip playground as a development build,
and surface the version string.

For some reason I had to install git in the build-playground phase of
the Docker build, to avoid errors from the Go command. I'm not sure why
this is, but it seems harmless.

For golang/go#48517

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