b26ac1c22f
This uses a new script and CircleCI job called "build-packages-dist" which shims the new Bazel build to produce outputs matching the legacy build. We'll use this to get AIO testing onto CircleCI as well. We move the integration tests to a new circleCI job that depends on this one, as well as the build publishing job. Note that every PR will have a trivial green publishing status, because we always create this job even for PRs. We'd rather not - see https://discuss.circleci.com/t/workflows-pull-request-filter/14396/4 PR Close #23512
35 lines
789 B
Bash
Executable File
35 lines
789 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -u -e -o pipefail
|
|
|
|
# Setup environment
|
|
readonly thisDir=$(cd $(dirname $0); pwd)
|
|
source ${thisDir}/_travis-fold.sh
|
|
|
|
|
|
# If the previous commands in the `script` section of .travis.yaml failed, then abort.
|
|
# The variable is not set in early stages of the build, so we default to 0 there.
|
|
# https://docs.travis-ci.com/user/environment-variables/
|
|
if [[ ${TRAVIS_TEST_RESULT=0} == 1 ]]; then
|
|
exit 1;
|
|
fi
|
|
|
|
|
|
# Don't deploy Angular.io if we are running in a fork
|
|
if [[ ${TRAVIS_REPO_SLUG} != "angular/angular" ]]; then
|
|
echo "Skipping deploy because this is not angular/angular."
|
|
exit 0
|
|
fi
|
|
|
|
|
|
case ${CI_MODE} in
|
|
aio)
|
|
travisFoldStart "deploy.aio"
|
|
(
|
|
cd ${TRAVIS_BUILD_DIR}/aio
|
|
yarn deploy-production
|
|
)
|
|
travisFoldEnd "deploy.aio"
|
|
;;
|
|
esac
|