commit | 6b2e7fc4ada41604973c29e5dcd7e0e1988373a1 | [log] [tgz] |
---|---|---|
author | Ravi Mistry <rmistry@google.com> | Tue Sep 03 09:23:04 2019 -0400 |
committer | Ravi Mistry <rmistry@google.com> | Tue Sep 03 13:47:30 2019 +0000 |
tree | 51ef5e70655ece4c02ab17ead8ca8837c03b01a3 | |
parent | 86a19c0ae5d7a7b219fcb85665d17d31643ef3f4 [diff] |
[CT] Run metrics analysis master script on swarming Part of the following dependent changes: [1] Add master instance type (https://skia-review.googlesource.com/c/buildbot/+/237804) [2] Makefile/Dockerfile/build_release changes to merge ct-master into ctfe (https://skia-review.googlesource.com/c/buildbot/+/237805) [3] Framework changes to support triggering master scripts on swarming (https://skia-review.googlesource.com/c/buildbot/+/237806) [4] Run lua master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237807) [5] Run admin tasks master scripts on swarming (https://skia-review.googlesource.com/c/buildbot/+/237808) [6] Run capture skps master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237809) [7] Run chromium analysis master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237810) [8] Run chromium builds master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237811) [9] Run chromium perf master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237812) [10] Run metrics analysis master script on swarming (https://skia-review.googlesource.com/c/buildbot/+/237877) [11] Display spinner when tasks are triggered from frontend pages (https://skia-review.googlesource.com/c/buildbot/+/237813) Bug: skia:9359 Change-Id: I77d2bc24cb9c0963171df840b502bf43bb1bba9d Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/237877 Reviewed-by: Ben Wagner aka dogben <benjaminwagner@google.com>
This repo contains infrastructure code for Skia.
The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone
or via go get
.
Using git clone
allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:
$ cd ${WORKDIR} $ git clone https://skia.googlesource.com/buildbot.git $ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR}) $ mkdir $GOPATH $ cd buildbot
Using go get
will fetch the repository into your GOPATH directory along with all the Go dependencies. You will need to set GOPATH and GO111MODULE=on. E.g.:
$ export GOPATH=${WORKDIR} $ export GO111MODULE=on $ go get -u -t go.skia.org/infra/... $ cd ${GOPATH}/src/go.skia.org/infra/
Note: go.skia.org is a custom import path and will only work if used like the examples here.
Install Node.js (not as root) and add the bin dir to your path. Optionally run npm install npm -g
, as suggested by the npm getting started doc.
Install other dependencies:
$ sudo apt-get install python-django $ go get -u github.com/kisielk/errcheck \ golang.org/x/tools/cmd/goimports \ go.chromium.org/luci/client/cmd/isolate $ npm install -g polylint bower
Build ~everything:
$ make all
Some code is generated using go generate
with external binaries. First, install the version of protoc referenced in the asset creation script and ensure it is on your PATH before other versions of protoc.
Install the necessary go packages:
$ go get -u \ github.com/golang/protobuf/protoc-gen-go \ golang.org/x/tools/cmd/stringer \ google.golang.org/grpc \ github.com/vektra/mockery/...
To generate code run in this directory:
$ go generate ./...
Install Cloud SDK.
Use this command to run the presubmit tests:
$ ./run_unittests --small