angular.js/lib, branch v1.2.0-rc.2 chore(grunt): support semver v2 version number format 2013-09-04T12:50:39+00:00 Igor Minar 2013-09-04T12:28:14+00:00 7b203fcff6dd01da0bebb43130a0e861c05c4e9c previously we couldn't use it because of bower bugs 
previously we couldn't use it because of bower bugs
chore(travis): clean up the build output 2013-08-28T22:46:19+00:00 Vojta Jina 2013-08-28T19:09:13+00:00 4138a80611bb7c74d0ac002d7220f99d03a08a59 






chore(travis): use ports proxied by SauceLabs
2013-08-28T22:46:19+00:00

Vojta Jina

2013-08-28T18:55:14+00:00

df17a2c7495cea22f803d1e2e22329712a7fd25a

Some browser does not allow to proxy localhost and so SL uses another proxy on the VM. This proxy only proxies some ports (SauceConnect proxies all ports).

This is the issue why Safari didn't connect for e2e tests, because 9877 was not proxied.

This change makes sure we use SL enabled ports.





Some browser does not allow to proxy localhost and so SL uses another proxy on the VM. This proxy only proxies some ports (SauceConnect proxies all ports).

This is the issue why Safari didn't connect for e2e tests, because 9877 was not proxied.

This change makes sure we use SL enabled ports.







chore(tests): add Promises/A+ Test Suite to the build
2013-08-24T19:49:57+00:00

James Talmage

2013-08-21T23:17:07+00:00

e848099d1bc0aacc6e940b1c14bf63eac97a66fb

Closes #3693





Closes #3693







chore(travis): clean up logs
2013-08-23T23:49:10+00:00

Vojta Jina

2013-08-21T10:16:57+00:00

80d0f98263786ef302ca7551c4515560a7c07195

Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build.





Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build.







chore: run more browsers on Travis (IE8,IE9,IE10,Safari,FF)
2013-08-23T23:49:10+00:00

Vojta Jina

2013-08-20T21:43:15+00:00

7909ebedc2a098f041dd2d3835e7297392bfdb7d

Also instead of running everything in parallel, there are only two parallel tasks:
- e2e tests running in the background (only on Chrome)
- all the unit tests running sequentially





Also instead of running everything in parallel, there are only two parallel tasks:
- e2e tests running in the background (only on Chrome)
- all the unit tests running sequentially







fix(grunt): fix regex in grunt util to handle pre-release versions
2013-08-15T19:41:14+00:00

Brian Ford

2013-08-13T20:17:09+00:00

fe267e30b95e8f48ddc670b97d485f18fb64d39e

NOTE: this also includes a temporary work-around for Bower





NOTE: this also includes a temporary work-around for Bower







chore(ngdocs): fixup the docs version switcher
2013-08-14T19:02:44+00:00

Igor Minar

2013-08-13T23:57:52+00:00

7215afa21c91c33c924a5aba7f3a704983642897












chore: disable npm install on Travis
2013-08-14T06:02:21+00:00

Vojta Jina

2013-08-13T22:14:55+00:00

c63fbbbcd1147c7e55c3e1d4118bd3a5f6059810

Grunt is configured to run `npm install` before every task. That is convenient when switching a branch for example.

On Travis, this makes no sense and is causing tons of NPM warnings (eg. packages not defining repository field etc).





Grunt is configured to run `npm install` before every task. That is convenient when switching a branch for example.

On Travis, this makes no sense and is causing tons of NPM warnings (eg. packages not defining repository field etc).







chore(sauce): use tunnel-identifier and ready-file only on Travis
2013-08-14T06:02:21+00:00

Vojta Jina

2013-08-13T04:29:20+00:00

c6ca827150fd98ffba3245e93f1245bdc07887b1

When running locally, there's not TRAVIS_JOB_NUMBER env variable defined and it screws
the Sauce Connect (it uses a tunnel with empty name), this makes it work locally without defining
TRAVIS_JOB_NUMBER env variable.

Also, if you run the sauce_connect_setup.sh locally, without having SAUCE_CONNECT_READY_FILE, it
does not pass the `--ready-file` argument to avoid Sauce Connect blowing up.





When running locally, there's not TRAVIS_JOB_NUMBER env variable defined and it screws
the Sauce Connect (it uses a tunnel with empty name), this makes it work locally without defining
TRAVIS_JOB_NUMBER env variable.

Also, if you run the sauce_connect_setup.sh locally, without having SAUCE_CONNECT_READY_FILE, it
does not pass the `--ready-file` argument to avoid Sauce Connect blowing up.