mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
31434943f1
Uploading payload size is unreliable from within Bazel. This is because tests might not run for every commit, tests might have been cached from a pull request RBE-build (causing payload uploading to be skipped most of the time as every change comes from a PR) We should disable the uploading as this is a fundamental problem (good thing to note now) that we can solve with better payload size tracking that we want to establish as part of dev-infra. PR Close #45446
24 lines
844 B
Bash
Executable file
24 lines
844 B
Bash
Executable file
#!/usr/bin/env bash
|
|
|
|
set -eu -o pipefail
|
|
|
|
# Source optional CI environment variables which are sandboxed out
|
|
# of the environment when running integration tests under Bazel
|
|
readonly bazelVarEnv="/tmp/bazel-ci-env.sh"
|
|
if [[ -f "$bazelVarEnv" ]]; then
|
|
source $bazelVarEnv
|
|
fi
|
|
|
|
# If running locally, at a minimum set PROJECT_ROOT
|
|
if [[ -z "${PROJECT_ROOT:-}" ]]; then
|
|
PROJECT_ROOT=$(cd $(dirname $0)/../..; pwd)
|
|
fi
|
|
|
|
# Bazel payload size tracking should always be treated as if this runs as part of
|
|
# a pull request. i.e. the results are not uploaded. This is necessary as Bazel test
|
|
# targets do not necessarily run for every commit, and cached results might originate
|
|
# from RBE-built pull requests. We will overhaut size-tracking anyway..
|
|
export CI_PULL_REQUEST="true"
|
|
|
|
source ${PROJECT_ROOT}/scripts/ci/payload-size.sh
|
|
trackPayloadSize "$@"
|