commit | f6482268101ca3e28bca39b04e8de69f7b1cfcba | [log] [tgz] |
---|---|---|
author | Alexander Rakoczy <alex@golang.org> | Tue Nov 23 11:35:36 2021 -0500 |
committer | Alexander Rakoczy <alex@golang.org> | Tue Nov 30 01:21:13 2021 +0000 |
tree | ac608819c56462e84f627791de11e37af556019f | |
parent | 9187f21bccb06608c7872ca8df444162eea55b38 [diff] |
deploy: add daily schedule for gotip playground Create a scheduled trigger to deploy the gotip playground every America/New_York morning. I attempted to create and manage the trigger with gcloud alpha builds triggers create scheduled, however I had to create the schedule portion manually in the web interface. There's probably a way to manage it with configuration in the CLI, but I added documentation to the Makefile on how to update it manually in the meantime. Create command: gcloud alpha builds triggers create scheduled --project=golang-org \ --schedule="15 11 * * *" \ --time-zone="America/New_York" \ --build-config=deploy/deploy_gotip.json \ --repo-type="CLOUD_SOURCE_REPOSITORIES" \ --revision="refs/heads/master" \ --repo-uri="https://source.developers.google.com/p/golang-org/r/playground" \ --name "playground-deploy-gotip-playground" \ --description="Deploy gotip playground daily" For golang/go#48517 Change-Id: I9d58e5a81ae4d590e6492c07cc71806864838c81 Reviewed-on: https://go-review.googlesource.com/c/playground/+/366634 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>
This subrepository holds the source for the Go playground: https://play.golang.org/
# build the image docker build -t golang/playground .
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
).
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.
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 .
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
To submit changes to this repository, see https://golang.org/doc/contribute.html.