We had some extra bazel options that don't seem to be necessary anymore now that we are using upstream bazel options appropriately. Retry the build a couple of times if it goes south, inside of the build image. This should allow re-use of the cache the second time, and if there is a temporary error, it should pick up and move forward. Change-Id: I5f304acb21fd3a4d40701fc0414ae0c424c838e5changes/12/678412/4
parent
80981a52c8
commit
56ceaf1c40
@ -0,0 +1,15 @@
|
||||
#!/bin/bash
|
||||
|
||||
set +x
|
||||
|
||||
for attempt in seq 1 3 ; do
|
||||
bazel build release \
|
||||
--define=ABSOLUTE_JAVABASE=/usr/lib/jvm/java-8-openjdk-amd64 \
|
||||
--javabase=@bazel_tools//tools/jdk:absolute_javabase \
|
||||
--host_javabase=@bazel_tools//tools/jdk:absolute_javabase \
|
||||
--host_java_toolchain=@bazel_tools//tools/jdk:toolchain_vanilla \
|
||||
--java_toolchain=@bazel_tools//tools/jdk:toolchain_vanilla \
|
||||
$@
|
||||
result=$?
|
||||
done
|
||||
exit $result
|
Loading…
Reference in new issue