aboutsummaryrefslogtreecommitdiffstats
path: root/.travis.yml
AgeCommit message (Collapse)Author
2014-02-26chore(travis): add gitter configIgor Minar
2014-02-21chore(travis): reorganize protractor configs to group by spec instead of by ↵Julie
browser 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.
2014-02-18chore(travis): don't run Travis-CI builds for G3 branchesCaitlin Potter
Building the G3 commits occupies a lot of time, and these branches have already been tested. Closes #6328
2014-02-16chore(travis): disable Safari and JQuery e2e tests on TravisPeter Bacon Darwin
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.
2014-02-07refactor(testing): split travis end to end tests into separate jobs for ↵Julie
jquery and jqlite Closes #6159
2014-02-06chore(travis): remove double bower install to test if it's still neededIgor Minar
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
2014-02-05refactor(testing): run end to end tests on separate browsers in parallelJulie
2014-01-31chore(travis): remove BrowserStack credentialsVojta Jina
Closes #5596
2013-12-11chore(scripts): refactor travis scriptsVojta Jina
Refactoring so that it's easier to use both SL/BS just depending on a global switch.
2013-12-11chore(travis): run two jobsVojta Jina
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.
2013-12-04chore(travis): move checks from before_scripts to scriptsVojta Jina
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
2013-12-03chore(travis): switch back to SauceLabsVojta Jina
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.
2013-11-25chore(travis): let's give BrowserStack a tryVojta Jina
Switch the build to use BrowserStack instead of SauceLabs. This also adds IE11 to our build.
2013-08-28chore(travis): run bower install twice to make sure it doesVojta Jina
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.
2013-08-28chore(travis): clean up the build outputVojta Jina
2013-08-23chore(travis): clean up logsVojta Jina
Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build.
2013-08-13chore: update Node.js on TravisVojta Jina
2013-07-30chore(bower): write grunt task for running bowerKen Sheedlo
2013-07-11chore(build): add check for merge conflicts, ddescribe, and iitBrian Ford
2013-07-02chore(travis): speed up the buildVojta Jina
- parallelize the tasks - cache requests (e2e tests) This reduces the time from ~18min to ~12min. It makes the output little messy. We could buffer output of each task and display it once it's fully finished, nicely. I think giving instant feedback is better.
2013-06-28chore: set up Sauce Labs with TravisVojta Jina
This should not affect the Jenkins build at all. Now, the Travis build uses Chrome on Sauce Labs, which in theory gives us opportunity to use any browser/platform that Sauce Labs offers.
2013-03-05chore(Grunt): switch from Rake to GruntDave Geddes
Migrates the Angular project from Rake to Grunt. Benefits: - Drops Ruby dependency - Lowers barrier to entry for contributions from JavaScript ninjas - Simplifies the Angular project setup and build process - Adopts industry-standard tools specific to JavaScript projects - Support building angular.js on Windows platform (really?!? why?!?) BREAKING CHANGE: Rake is completely replaced by Grunt. Below are the deprecated Rake tasks and their Grunt equivalents: rake --> grunt rake package --> grunt package rake init --> N/A rake clean --> grunt clean rake concat_scenario --> grunt build:scenario rake concat --> grunt build rake concat_scenario --> grunt build:scenario rake minify --> grunt minify rake version --> grunt write:version rake docs --> grunt docs rake webserver --> grunt webserver rake test --> grunt test rake test:unit --> grunt test:unit rake test:<jqlite|jquery|modules|e2e> --> grunt test:<jqlite|jquery|modules|end2end|e2e> rake test[Firefox+Safari] --> grunt test --browsers Firefox,Safari rake test[Safari] --> grunt test --browsers Safari rake autotest --> grunt autotest NOTES: * For convenience grunt test:e2e starts a webserver for you, while grunt test:end2end doesn't. Use grunt test:end2end if you already have the webserver running. * Removes duplicate entry for Describe.js in the angularScenario section of angularFiles.js * Updates docs/src/gen-docs.js to use #done intead of the deprecated #end * Uses grunt-contrib-connect instead of lib/nodeserver (removed) * Removes nodeserver.sh, travis now uses grunt webserver * Built and minified files are identical to Rake's output, with the exception of one less character for git revisions (using --short) and a couple minor whitespace differences Closes #199
2012-09-24chore: add travis configVojta Jina