angular.js/.travis.yml, branch v1.2.15 chore(travis): add gitter config 2014-02-26T22:12:07+00:00 Igor Minar 2014-02-26T22:11:39+00:00 73daa79e911260fc177727238c3e780e8043244e 






chore(travis): reorganize protractor configs to group by spec instead of by browser
2014-02-22T00:57:04+00:00

Julie

2014-02-20T05:01:54+00:00

39c82f3fb7a8459304d5e07dc87bd0623ad1efd0

Use the multiConfiguration ability of Protractor to start tests on multiple browsers
from the same travis cell. Group tests by type (jquery, jqlite, or docs tests) instead
of by browser. Turn on tests for jQuery.





Use the multiConfiguration ability of Protractor to start tests on multiple browsers
from the same travis cell. Group tests by type (jquery, jqlite, or docs tests) instead
of by browser. Turn on tests for jQuery.







chore(travis): don't run Travis-CI builds for G3 branches
2014-02-19T00:15:50+00:00

Caitlin Potter

2014-02-19T00:05:27+00:00

a3f70172ef23585399f24011f72948f894e31e6f

Building the G3 commits occupies a lot of time, and these branches have
already been tested.

Closes #6328





Building the G3 commits occupies a lot of time, and these branches have
already been tested.

Closes #6328







chore(travis): disable Safari and JQuery e2e tests on Travis
2014-02-16T19:03:45+00:00

Peter Bacon Darwin

2014-02-16T18:23:38+00:00

49f90e559ed412402ad7444bc2db2bc1c182ddf5

There are no real JQuery tests at this point anyway and the Safari that we
are getting from SauceLabs seems to be a flakey Windows 2000 version that
is not necessarily providing accurate results.





There are no real JQuery tests at this point anyway and the Safari that we
are getting from SauceLabs seems to be a flakey Windows 2000 version that
is not necessarily providing accurate results.







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.