angular.js/.travis.yml, branch v1.2.13 refactor(testing): split travis end to end tests into separate jobs for jquery and jqlite 2014-02-08T04:41:39+00:00 Julie 2014-02-06T19:29:24+00:00 e645f7cae14618bd8fc7d6b3eadf9307f5a1aeb7 Closes #6159 
Closes #6159
chore(travis): remove double bower install to test if it's still needed 2014-02-06T10:31:23+00:00 Igor Minar 2014-02-06T10:31:23+00:00 e609239fab46d7f8af195a69756c91b4f66c8463 We did this due to travis-ci/travis-ci#1293 but since it's possible that this hack is not needed, I'm removing it. If it turns out that we do need it still then we should ping the travis issue and revert this commit 
We did this due to travis-ci/travis-ci#1293 but since it's possible that this hack is not needed, I'm removing it.

If it turns out that we do need it still then we should ping the travis issue and revert this commit
refactor(testing): run end to end tests on separate browsers in parallel 2014-02-05T23:40:16+00:00 Julie 2014-01-31T06:09:09+00:00 84467d869730c6821c07496f510355ab73e7c10b 






chore(travis): remove BrowserStack credentials
2014-01-31T15:48:36+00:00

Vojta Jina

2014-01-31T15:48:36+00:00

c22ab5d2e28605462ba77f6c02e99efdd24338a3

Closes #5596




Closes #5596






chore(scripts): refactor travis scripts
2013-12-11T18:12:18+00:00

Vojta Jina

2013-12-11T17:56:06+00:00

8864e54f1f94883f3e22d7ce7ed87a699467a217

Refactoring so that it's easier to use both SL/BS just depending on a global switch.




Refactoring so that it's easier to use both SL/BS just depending on a global switch.






chore(travis): run two jobs
2013-12-11T18:02:14+00:00

Vojta Jina

2013-12-11T09:02:56+00:00

dc4df931778a374f1fb3c8af7545733c09b9c098

Instead of parallelization on a single Travis VM, we use two VMs.
- output is nicer (we don't have to buffer e2e tests and then show it at the end)
- you can easily see faster the result of unit tests (as it's basically a separate build)

We should also make sure we only do the necesary stuff (for install we don't need to do `grunt
package` for unit tests, we only need to generate the docs for e2e tests.





Instead of parallelization on a single Travis VM, we use two VMs.
- output is nicer (we don't have to buffer e2e tests and then show it at the end)
- you can easily see faster the result of unit tests (as it's basically a separate build)

We should also make sure we only do the necesary stuff (for install we don't need to do `grunt
package` for unit tests, we only need to generate the docs for e2e tests.







chore(travis): move checks from before_scripts to scripts
2013-12-05T06:53:54+00:00

Vojta Jina

2013-12-05T06:53:28+00:00

21e48abbc1e75ace1b6b99c7b19f538d4e792068

If jshint (or any other ci-check) fails, Travis marks the build as "Errored" which I don't think is desider:
https://travis-ci.org/angular/angular.js/builds/14938896





If jshint (or any other ci-check) fails, Travis marks the build as "Errored" which I don't think is desider:
https://travis-ci.org/angular/angular.js/builds/14938896







chore(travis): switch back to SauceLabs
2013-12-03T23:49:19+00:00

Vojta Jina

2013-12-03T20:15:36+00:00

6127528b5008a507966c7f1a1030db27ca2fbc0b

I think we are pretty close to be able to use both.

The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.





I think we are pretty close to be able to use both.

The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.







chore(travis): let's give BrowserStack a try
2013-11-25T23:19:28+00:00

Vojta Jina

2013-11-20T00:50:23+00:00

ffd075b44010102e628ce3ade9a54bfde80fdd76

Switch the build to use BrowserStack instead of SauceLabs.

This also adds IE11 to our build.




Switch the build to use BrowserStack instead of SauceLabs.

This also adds IE11 to our build.






chore(travis): run bower install twice to make sure it does
2013-08-29T00:48:46+00:00

Vojta Jina

2013-08-29T00:48:46+00:00

3379eebe4bca22316327b7f1ca92c2240b29187c

This is a work-around for Bower/Node.js issue (https://github.com/bower/bower/issues/830). We run `bower install` twice, as the probability of failing twice in a row is very low.

I had to extract `bower` task out of the package, because we need to run `bower install` before building and `grunt bower` can fail, which takes down the whole process and therefore it wouldn't build.





This is a work-around for Bower/Node.js issue (https://github.com/bower/bower/issues/830). We run `bower install` twice, as the probability of failing twice in a row is very low.

I had to extract `bower` task out of the package, because we need to run `bower install` before building and `grunt bower` can fail, which takes down the whole process and therefore it wouldn't build.