Travis

We're integrated with Travis to run tests in the cloud. On every commit and every pull request Travis inspects the contents of .travis.yml (on each branch!) and runs tests. It's set up for both mod_pagespeed and ngx_pagespeed:

• mod_pagespeed: travis dashboard, .travis.yml
• ngx_pagespeed: travis dashboard, .travis.yml

These are configured to send status emails to the pagespeed-ci@googlegroups.com mailing list, which anyone is welcome to join. If you're developing a change and pushing intermediate results to github it's polite to change the notifications email in .travis.yml to your own email address, so that you don't spam everyone with your build/test failures.

Travis has an effective timeout of just under 50min, which we hit occasionally. We've discussed paying for Travis, to get a 120min timeout, but for now we've gotten our builds to finish within the time window almost all the time. (This is hard to optimize with, because building all our stuff takes almost all of the 50min, and running tests is relatively fast.)

More Travis docs: https://docs.travis-ci.com/user/customizing-the-build/