* Saucelabs seems to have issues with Edge and the `karma-coverage` plugin.
* Running on Browserstack seems to be work without any flakiness and also makes the build faster (runs less browsers than on saucelabs)
* Updates the saucelabs tunnel binaries to fix CI flakiness for unit tests and protractor.
From what we experience, older versions of Saucelabs tend to cause flakiness immediately (See `master` branch)
* Currently we are publishing to `DevVersion/material-builds` for testing purposes and everything seems to work as expected.
* Switching the repository to the `material2-builds` repository on the Angular organization
* When retrieving the last commit message, the script currently pipes it through the head command.
Since the git log command using the less command will exit immediately the pipe will fail with a 141 exit code (because it can't read from a closed stream)
* Currently the Travis CI leader mode can timeout, because the `e2e modes` runs longer than 10 minutes and the leader mode then needs to wait the same time (just without any output).
Travis stops the build automatically when there is no output for the last 10 minutes.
* The plugin `travis-after-modes` has been updated to log a message (like a progress-bar) each time the modes are checked again.
The recently added script for the per-commit publishing is not properly checking for the environment variable.
This means that the per-commit packages can be not created yet.
* chore: create build artifacts for each commit
* Switch to new npm package
* Update version to latest
* Publish the builds after all modes succeeded.
* Address comments
* Change snake_case to camelCase
* chore: remove inactive browserstack wrapper package
No longer uses the "inactive" browserstack wrapper package from npm,
which was just responsible for creating the readyfile.
We can create the readyfile ourself and get rid of the npm package.
* Fix incorrect comments
* Don't wait for tunnel if timer exceeded
* Fix race conditions
* Add empty line before logging that the tunnel is ready.
* chore(forbidden-identifiers): detect incorrect line endings
* Removes stale scope checking (from `@angular2-material/$COMPONENT` times)
* Adds support for error grouping (useful when having a file full of invalid line endings)
* Moves chains into exta functions to understand procession easily.
* Update comment wording
* fix(button): remove relative import from other scope.
* Removes invalid relative import from other scope.
* Forbidden identifiers should run against all sources when not checking a PR.
* Cleanup Forbidden identifiers script, by using ES6 arrow functions.
Fixes#967.
* chore(changelog): properly name tags for github compare links
* The convention changelog currently auto-prefixes the previous semver tag with a `v`, which causes the github compare links to not work.
* Manually resolve the previous and current tag from the git metadata. (As in https://github.com/angular/material/pull/9264)
* Remove prefixed compare links in previous generated chaneglog
* Change `getTags` to `getAvailableTags`
* Add comment explaining how we resolve the tags
> Removes the module ids of the component metadata.
> Since the templates and styles are now inlined, the module id has become unnecessary and
> can cause unexpected issues
This also fixes https://github.com/angular/material2/issues/974 in meanwhile.
* update stage-release to include .metadata.json files
* bump version from alpha.6 to alpha.6-2
* remove test files from packages
* add skipTemplateCodegen option
* add desc to enact-release script
* improve script comments
* chore: update angular-cli version
* tests are passing
* use straight jasmine functions
* remove deprecated methods
* remove use of new Provider(...)
* fix tests that relied on returning a promise
* debugging ios8
Change the template regex to support minified js files. This partially addresses inlining resources for an angular-cli prod build.
(cherry picked from commit ba47c8d)
Paul Gschwendtner