* Disable spammy logs in release
The `debug` flag does not impact the result of the build, but it does turn on ~every logging option in bazel resulting in 200k lines of logs each run
* Update scripts/release-binary.sh
Co-authored-by: Keith Mattix II <keithmattix@microsoft.com>
---------
Co-authored-by: Keith Mattix II <keithmattix@microsoft.com>
* configure asan
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix
Signed-off-by: Kuat Yessenov <kuat@google.com>
* test
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix asan
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix asan
Signed-off-by: Kuat Yessenov <kuat@google.com>
* test
Signed-off-by: Kuat Yessenov <kuat@google.com>
* asan
Signed-off-by: Kuat Yessenov <kuat@google.com>
* test
Signed-off-by: Kuat Yessenov <kuat@google.com>
* update
Signed-off-by: Kuat Yessenov <kuat@google.com>
* try asan again
Signed-off-by: Kuat Yessenov <kuat@google.com>
* force rpath
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix arm
Signed-off-by: Kuat Yessenov <kuat@google.com>
---------
Signed-off-by: Kuat Yessenov <kuat@google.com>
Two parts:
* Cleanup DOCKER_REPOSITORY, which is strictly dead code
* Cleanup WASM_REPOSITORY, which is used to push WASM images. This has
moved to istio-ecosystem
* fix ARM format script
Signed-off-by: Kuat Yessenov <kuat@google.com>
* use image clang
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix buildifier
Signed-off-by: Kuat Yessenov <kuat@google.com>
* make manual
Signed-off-by: Kuat Yessenov <kuat@google.com>
* disable wasm build unless needed
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix
Signed-off-by: Kuat Yessenov <kuat@google.com>
---------
Signed-off-by: Kuat Yessenov <kuat@google.com>
* ci: save dwp files
Signed-off-by: Kuat Yessenov <kuat@google.com>
* release asan
Signed-off-by: Kuat Yessenov <kuat@google.com>
Signed-off-by: Kuat Yessenov <kuat@google.com>
* release: allow publishing without check
This allows non-official Istio AMD64 CI to publish without this check.
IMO a flag that is "skip checks" means we know what we are doing, and
should be allowed to skip+publish if we explicitly specify it. This will
be needed for arm64 builds where we cannot use Xenial
* update comment
* add extensions config
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* add missing WORKSPACE
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* exclude extensions_build_config.bzl
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* move extension and contrib to public visibility
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* add LastFlag verification script
* use trap on exit in verify-last-flag-matches-upstream.sh
* add verify-last-flag script to the lint target
* use set -x in verify-last-flag script
* make verify-last-flag-matches-upstream.sh executable
* split @com_googlesource_chromium_v8//:build into seperate step
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* address comment
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* prerun v8//:build almost everywhere
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* also push-debian.sh
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
* also docker
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
The build is green but its overwriting the ubunutu image since we didn't
properly pull the BINARY_NAME option that was added through to all
locations (and had a naming conflict). I think this should be the last
change needed but unfortunately its a bit hard to test postsubmit jobs
John Howard