70303fc210
The build dashboard can be used to view builds for the main Go repo and other golang.org/x repos. The isUntested invocation was invalid for repos other than the main one, which was causing results for some tested configurations to become hidden (incorrectly replaced by '•'). Larger changes are needed before there's sufficient data to compute the GoBranch value for all repos reliably, so for now, just update the isUntested invocation to apply only for the main repo. This prioritizes the ability to view test results over the ability to see that some builds are intentionally missing because they are configured not to run. Doing both is a part of future work. For golang/go#40290. For golang/go#34744. For golang/go#28643. Change-Id: Id43cb47abacb1036f578efbb8232ae17ad40eca9 Reviewed-on: https://go-review.googlesource.com/c/build/+/244137 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> |
||
|---|---|---|
| .. | ||
| static | ||
| .gcloudignore | ||
| Makefile | ||
| README.md | ||
| app.yaml | ||
| build.go | ||
| cron.sh | ||
| dash.go | ||
| handler.go | ||
| index.yaml | ||
| ui.go | ||
| ui.html | ||
| ui_test.go | ||
README.md
build.golang.org App Engine App
This is the code that runs https://build.golang.org/
Local development
To use production maintner data (for the GetDashboard RPC containing the list of commits, etc) and production active builds (from the coordinator), both of which are open to anybody, use:
go run . --dev --fake-results
If you also want to use the production datastore for real commit data, or you want to work on the handlers that mutate data in the datastore, use:
go run . --dev
That requires access to the "golang-org" GCP project's datastore.
Environment variables you can change:
PORT: plain port number or Go-style listen addressDATASTORE_PROJECT_ID: defaults to"golang-org"in dev modeMAINTNER_ADDR: defaults to "maintner.golang.org"
Deploying a test version
To deploy to the production project but to a version that's not promoted to the default URL:
make deploy-test
It will tell you what URL it deployed to. You can then check it and either delete it or promote it with either the gcloud or web UIs. Or just ignore it. They'll scale to zero and are only visual clutter until somebody deletes a batch of old ones.
Deploying to production
To deploy to https://build.golang.org:
make deploy-prod