iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3,912 Commits 5 Branches 1 Tag 142 MiB
Commit Graph

11 Commits

Author SHA1 Message Date
Igor Minar 912717ff31 ci(analytics): fix TRAVIS_PULL_REQUEST reporting 
process.env.TRAVIS_PULL_REQUEST contains a string and not a boolean value, so we need
to compare it to a string literal rather than do boolean arithmetics.
 2016-03-05 19:54:22 +00:00
Brian Ford 6cfc6f5bb2 build(npm): upgrade to npm v3 
Closes #3193
 2016-01-22 03:25:32 +00:00
Tim Blasi 31f85f0297 chore(analytics): Build hello_world, check constraints 
Create gulp targets to build `hello_world` and check its gzipped size
against size constraints.

See #5312, #5314
 2015-11-23 20:10:04 +00:00
Tim Blasi 225b9d306b chore(analytics): Generalize file size analytics 
Move file size analytics code into a reusable module.

See #5312, #5314
 2015-11-23 20:10:04 +00:00
Igor Minar 41dfaf393b build(analytics): track bundle size 
This will send bundle sizes (before and after gzip) to Google Analytics so that we can
track bundle size over time for every bundle we produce.

Closes #5294
 2015-11-16 21:42:50 +00:00
vsavkin 6d70cd78ec fix(build): fix npm install not to depend on minimist 
Closes #5282
 2015-11-13 23:56:43 +00:00
Igor Minar 2ecbd0eaaf build(analytics): fix bug that prevented us from collecting OS info 2015-11-13 22:50:38 +00:00
Igor Minar 8ab7781b2d build(analytics): keep track of --projects value via a custom dimension 2015-11-13 22:50:38 +00:00
Igor Minar b329a58416 build(analytics): track TRAVIS_JOB_NUMBER as a custom dimension 2015-10-29 13:53:21 +00:00
Igor Minar ae7f76e91f build(analytics): add support for tracking npm installs 
Since the very first npm install is called while node_modules is empty, we need to ignore it, but we can track
the start timestamp and record the install even once the installation is completed.
 2015-10-29 13:53:21 +00:00
Igor Minar da1272f368 build(analytics): add basic build-analytics to the project 
This is pretty experimental, but the goal is to track the performance
of our build over time so that we can more easily track perf regressions.

Currently it's integrated only with gulp tasks, but I'd like to expand it
to tracking travis jobs, protractor/benchpress test runs, npm installs, etc.

No PII is being collected. And the data is collected via a Google Analytics
property owned by the Angular team account.

Closes #4672
 2015-10-12 03:50:00 +00:00