556350de37
We have a similar ingestion strategy to Gold. I tried to use something off the shelf like benchmark.js but passing the PathKit context into the benchmarks was non-trivial. Plus, making a basic benchmarking tool ended up being not too hard. We should be able to re-use the docker container/aggregator for CanvasKit too. Bug: skia: Change-Id: I613dfc58ea57c31cf71566a8ac55f8df9272ad25 Reviewed-on: https://skia-review.googlesource.com/c/161620 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com>
27 lines
1.2 KiB
Makefile
27 lines
1.2 KiB
Makefile
gold_docker_image: aggregator
|
|
# Set the build context to the current work dir, so we can copy
|
|
# the built binary to where we need it.
|
|
docker build -t gold-karma-chrome-tests -f ./docker/gold-karma-chrome-tests/Dockerfile .
|
|
|
|
perf_docker_image: aggregator
|
|
# Set the build context to the current work dir, so we can copy
|
|
# the built binary to where we need it.
|
|
docker build -t perf-karma-chrome-tests -f ./docker/perf-karma-chrome-tests/Dockerfile .
|
|
|
|
aggregator:
|
|
mkdir -p ./tmp
|
|
CGO_ENABLED=0 GOOS=linux go build -o ./tmp/gold-aggregator -a ./gold/
|
|
mkdir -p ./tmp
|
|
CGO_ENABLED=0 GOOS=linux go build -o ./tmp/perf-aggregator -a ./perf/
|
|
|
|
# Can check CHROME_VERSION with
|
|
# docker run karma-chrome-tests /usr/bin/google-chrome-stable --version
|
|
CHROME_VERSION=68.0.3440.106_v5
|
|
|
|
publish_gold_karma_chrome_tests: gold_docker_image
|
|
docker tag gold-karma-chrome-tests gcr.io/skia-public/gold-karma-chrome-tests:${CHROME_VERSION}
|
|
docker push gcr.io/skia-public/gold-karma-chrome-tests:${CHROME_VERSION}
|
|
|
|
publish_perf_karma_chrome_tests: perf_docker_image
|
|
docker tag perf-karma-chrome-tests gcr.io/skia-public/perf-karma-chrome-tests:${CHROME_VERSION}
|
|
docker push gcr.io/skia-public/perf-karma-chrome-tests:${CHROME_VERSION}
|