commit | 47e3df904f64fd1a2c2d7b1675e43ed9bf1bde5c | [log] [tgz] |
---|---|---|
author | Kevin Lubick <kjlubick@google.com> | Wed Jul 29 10:11:46 2020 -0400 |
committer | Kevin Lubick <kjlubick@google.com> | Wed Jul 29 16:24:02 2020 +0000 |
tree | 3384e0327d799c330281903cf10301e3c2a2375a | |
parent | 60cacc805066b9a44b336b66dd955c932fd6173e [diff] |
[gold] Support multiple CRS systems While not the most elegant solution, I found this to be the easiest - bundling up the important CRS related objects and passing around lists of these where applicable. A follow-on CL will update all the lit-html pages to include crs in the state. There's an update to goldctl to provide crs when triaging and for getting expectations. One the remaining polymer pages are ported and the goldctl change is rolled out, we can remove the code that defaults the selection to the first review system (included for backwards compatibility). Change-Id: I3d503366091798b757e9fbeec4894b69dc0e4a50 Bug: skia:10532 Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/306067 Reviewed-by: Leandro Lovisolo <lovisolo@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