build: load angular.js minified output in upgrade tests

[devversion]

We should try loading Angular.JS for the upgrade tests in their minfied output.

There seems to be a lot flakiness in regards to loading AngularJS within Travis, and the onerror messages aren't really too helpful. In order to reduce the payload that will be passed through the Saucelabs tunnel, we should try to load the minfied output files.

[mary-poppins]

You can preview b59c2c1 at https://pr27711-b59c2c1.ngbuilds.io/.

[gkalpak]

As discussed "offline", this change will make it harder to debug failing tests locally, but is worth it if it will make the CI more stable.

Could you make it easier to switch to the none-minified version (for when we want to run and debug tests locally). E.g. serve both minified and non-minified files and have a flag in test_helpers.ts the determines which ones to use. (It will use the minified ones, but we would be able to switch to non-minified by flipping that flag.

[devversion]

@gkalpak That sounds like a good idea. How would that work with the Bazel and Karma configuration? Should we just add the unminifed Angular versions to the karma config? (they won't be included anyway)

And for Bazel, we can just declare the unminfied Angular version also as srcs, but that feels like an anti-pattern. Any ideas?

[gkalpak]

I don't know much about bazel, but my thought was including both minified and non-minified (to both karma files and bazel). I don't think bazel will mind and those files will change very infrequently.

[mary-poppins]

You can preview 1593da4 at https://pr27711-1593da4.ngbuilds.io/.

[devversion]

@gkalpak Addressed your feedback.

[IgorMinar]

thanks

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}