tree: 1a66c8215f4394ac42472c90758b10966d982f13 [path history] [tgz]
  1. OWNERS
  2. PRESUBMIT.py
  3. README.md
  4. cmd/
  5. default/
  6. goenv.sh
  7. gopath/
appengine/chromium_build_stats/README.md

This is an application designed to collect and analyze build/compile stats.

Deign Doc: Chromium build time profiler

default module in default/ dir

How to:

to generate trace-viewer contents $ cd default; go generate it will use ../third_party/catapult/tracing/bin/trace2html

to compile $ cd default; ../goenv.sh goapp build

to run locally with dev_appserver (note: no service account available, so you couldn't fetch file from gs://chrome-goma-log) $ ./goenv.sh goapp serve default (or $ cd default; ../goenv.sh goapp serve )

to deploy to production $ ./goenv.sh goapp deploy default (or $ cd default; ../goenv.sh goapp deploy ) NOTE: Check ninja trace data after deploy. If it's not accessible, you must forget to generate trace-viewer contents (See the first item of this how-to). Re-generate it and deploy again.

to run gofmt $ cd default; ../goenv.sh goapp fmt

$ goenv.sh goapp fmt logstore ninjalog

to run govet $ cd default; ../goenv.sh goapp vet

$ goenv.sh goapp vet logstore ninjalog

to run test $ cd default; ../goenv.sh goapp test

to read go documentation

$ ./goenv.sh godoc $ ./goenv.sh godoc (or $ ./goenv.sh godoc -http :6060 and go to http://localhost:6060 )