angular-cn/scripts/ci/test-aio-tools.sh

#!/usr/bin/env bash

set -u -e -o pipefail

# Setup environment
readonly thisDir=$(cd $(dirname $0); pwd)
source ${thisDir}/_travis-fold.sh


travisFoldStart "test.docs"
  (
    cd ${PROJECT_ROOT}/aio
    yarn setup
    yarn tools-test
  )
travisFoldEnd "test.docs"
ci(aio): run docs-tests in travis (#14097) 2017-01-25 17:27:05 -05:00			`#!/usr/bin/env bash`

ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425) 2017-03-02 03:22:24 -05:00			`set -u -e -o pipefail`
ci(aio): run docs-tests in travis (#14097) 2017-01-25 17:27:05 -05:00
			`# Setup environment`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`readonly thisDir=$(cd $(dirname $0); pwd)`
			`source ${thisDir}/_travis-fold.sh`
ci(aio): run docs-tests in travis (#14097) 2017-01-25 17:27:05 -05:00

ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425) 2017-03-02 03:22:24 -05:00			`travisFoldStart "test.docs"`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`(`
			`cd ${PROJECT_ROOT}/aio`
build(docs-infra): display github links in CLI API docs (#26515) This commit includes the following changes: * CLI version information is read from the CLI package from which we read the help files. * CLI API pages now contain GH links * line numbers are not shown in GH links, if the doc does not have a truthy `startingLine` value. This allows us to remove hard coded checks for `guide` pages * content pages and CLI api docs no longer have a `startingLine` * the hard-coded `packages` path segment has been removed from the templates; instead we now only use the `realProjectRelativePath`. * the `realProjectRelativePath` has been updated accordingly for API and CLI API docs. PR Close #26515 2018-10-17 10:45:47 -04:00			`yarn setup`
ci(aio): compute AIO deployment mode There are now 3 modes for deployment: next, stable, archive. We compute which mode (and other deployment properties) from the `TRAVIS_BRANCH` and the `STABLE_BRANCH`. If the TRAVIS_BRANCH is master we deploy as "next". If the `TRAVIS_BRANCH` matches the `STABLE_BRANCH` we deploy as "stable". Otherwise if the branch has a major version lower than the stable version and its minor version is highest of similar branches we deploy as "archive". For "archive" deployments we compute the firebase project and deployment url based on the major version of the `TRAVIS_BRANCH`. As well as choosing where to deploy the build, we also use this to select the environment file for the AIO Angular app. This will enable the app to change its rendering and behaviour based on its mode. See #18287 Closes #18297 2017-07-28 06:57:44 -04:00			`yarn tools-test`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`)`
ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425) 2017-03-02 03:22:24 -05:00			`travisFoldEnd "test.docs"`