angular-docs-cn/scripts
George Kalpakas b6dfc8b08c ci: log calculated file sizes for each build (#33099)
The `payload-size.sh` script is mainly used on CI to calculate, check
and potentially save (on non-PR builds) the sizes of the bundles for
various apps (including angular.io). If everything goes well (i.e. the
checks pass, meaning that the sizes did not increase above the specified
threshold) nothing is shown in the CI logs.

In some cases, it is useful to be able to see what the sizes were in a
specific build; e.g. for debugging purposes or when investigating a
gradual increase that happened over time. (Some of this info is
available on https://size.angular.io/, but not all.)

Previously, the only way to find out what the sizes were for a specific
build was to checkout the corresponding commit locally and build the
target app, which in turn requires building all Angular packages and can
take some time. Given that the sizes are already calculated on CI, this
was a waste.

This commit makes it easy to find out the bundle sizes for a specific
build/commit by always printing out the calculated sizes (thus making
them show up in the CI logs).

PR Close #33099
2019-10-15 16:48:29 +00:00
..
browserstack
ci ci: log calculated file sizes for each build (#33099) 2019-10-15 16:48:29 +00:00
git build: mention where to find the invalid commit message, when validation fails (#32420) 2019-08-30 13:52:54 -04:00
github build: update base SHA for rebase on merge-pr script 2019-05-21 17:07:19 -07:00
jenkins
local-dev build: create script for setting up RBE in local dev environment (#31200) 2019-10-03 12:17:56 -07:00
release build: add pre-release check that validates the version name (#29551) 2019-03-27 12:26:13 -07:00
saucelabs ci: move bazel saucelabs execution to script to be used across all Angular repos (#32141) 2019-08-16 09:57:23 -07:00
build-ivy-npm-packages.sh build: allow build-packages-dist.sh to be run from anywhere (#29092) 2019-03-20 14:45:54 -04:00
build-packages-dist.sh build: allow build-packages-dist.sh to be run from anywhere (#29092) 2019-03-20 14:45:54 -04:00
package-builder.sh ci: run bazel for package-builder via yarn rather than binary directly (#32983) 2019-10-10 13:57:54 -07:00