Russ Cox 12c3afc1ae dashboard: fix for branches ... In the new world, one builder runs gobuilder -commit which uploads information about commits to the dashboard, which then hands the work out to the builders by hash. There is no assumption anymore that the commit numbers are consistent across builders. New builders will need to be deployed. For now darwin-amd64 is running the new builder to test the code. The new JSON-based protocol for handing out work via /todo should be easy to extend if we want to add support for sending trial CLs to the builders. This code is already running on godashboard.appspot.com. R=adg, dave CC=golang-dev https://golang.org/cl/4519047		2011-05-12 11:21:34 -04:00
..
static
_multiprocessing.py
app.yaml	dashboard: fix for branches	2011-05-12 11:21:34 -04:00
const.py	misc/dashboard: tweak build fail notification email	2011-02-19 07:37:24 +11:00
fail-notify.txt	misc/dashboard: notify golang-dev on build failure	2011-02-18 03:34:22 +11:00
gobuild.py	dashboard: fix for branches	2011-05-12 11:21:34 -04:00
index.yaml	dashboard: fix for branches	2011-05-12 11:21:34 -04:00
key.py.dummy
main.html	dashboard: build most recent revision first	2011-04-25 23:48:06 -04:00
package.html	dashboard: build most recent revision first	2011-04-25 23:48:06 -04:00
package.py	godashboard: Show packages at launchpad.net	2011-04-13 10:34:35 +10:00
project-edit.html
project-notify.txt
project.html	dashboard: build most recent revision first	2011-04-25 23:48:06 -04:00
toutf8.py