gecko-dev/servo/.travis.yml

language: python

matrix:
  fast_finish: true
  include:
    - sudo: false
      script: ./mach test-tidy
      cache: false
    - sudo: 9000
      dist: trusty
      script:
         - ./mach build -d --verbose
         - bash etc/ci/lockfile_changed.sh
         - bash etc/ci/manifest_changed.sh          
      cache:
        directories:
          - .cargo
          - .servo
          - $HOME/.ccache
      env: CCACHE=/usr/bin/ccache
      addons:
        apt:
          packages:
            - cmake
            - freeglut3-dev
            - gperf
            - libosmesa6-dev
            - python-virtualenv
            - xorg-dev
            - ccache

branches:
  only:
    - master
servo: Merge #5213 - Check tidy in Travis file (from servo:tidy-travis); r=Ms2ger Source-Repo: https://github.com/servo/servo Source-Revision: a2ff1aae824d736922616cd8a592fd7d93361fa7 2015-03-14 15:54:48 +03:00			`language: python`
servo: Merge #7915 - Build Servo on Travis (from frewsxcv:travis); r=larsbergstrom Closes #6962 Source-Repo: https://github.com/servo/servo Source-Revision: e5b46eb919461531b8bf5a79fc0c5e6e1ec94c75 2015-10-08 18:00:28 +03:00
			`matrix:`
			`fast_finish: true`
			`include:`
servo: Merge #7974 - Use Travis container-based infra for test-tidy (from frewsxcv:travis); r=jdm I wasn't aware one could specify options like `sudo` and `services` on a per build-environment basis. Since the container-based builds are faster than normal builds, we should utilize it for test-tidy Source-Repo: https://github.com/servo/servo Source-Revision: 9c1cb9f61e3d7a34fa49355d28d9edc236c0690f 2015-10-11 18:17:25 +03:00			`- sudo: false`
servo: Merge #8036 - Travis CI building cleanup, enable caching (from frewsxcv:travis); r=metajack The only reason the Dockerfile was introduced is because the default machines that Travis uses are based on Ubuntu 12.04, which has some very old incompatible dependencies with Servo. Docker allowed use to use a new version of Ubuntu, allowing us to compile with ease. I just learned that they are currently beta testing 14.04 support: http://docs.travis-ci.com/user/trusty-ci-environment/ This commit updates our Travis config to remove our dependency on Docker and just build directly on the images, reducing some complexity and also overhead of downloading Docker images. In addition, this commit also enables caching of the .servo and .cargo directories on Travis in an attempt to reduce build times. http://docs.travis-ci.com/user/caching/#Arbitrary-directories Source-Repo: https://github.com/servo/servo Source-Revision: 628c2a04326b27ac2743771dca52612c8ce30ad2 2015-10-16 23:09:36 +03:00			`script: ./mach test-tidy`
			`cache: false`
servo: Merge #7974 - Use Travis container-based infra for test-tidy (from frewsxcv:travis); r=jdm I wasn't aware one could specify options like `sudo` and `services` on a per build-environment basis. Since the container-based builds are faster than normal builds, we should utilize it for test-tidy Source-Repo: https://github.com/servo/servo Source-Revision: 9c1cb9f61e3d7a34fa49355d28d9edc236c0690f 2015-10-11 18:17:25 +03:00			`- sudo: 9000`
servo: Merge #8036 - Travis CI building cleanup, enable caching (from frewsxcv:travis); r=metajack The only reason the Dockerfile was introduced is because the default machines that Travis uses are based on Ubuntu 12.04, which has some very old incompatible dependencies with Servo. Docker allowed use to use a new version of Ubuntu, allowing us to compile with ease. I just learned that they are currently beta testing 14.04 support: http://docs.travis-ci.com/user/trusty-ci-environment/ This commit updates our Travis config to remove our dependency on Docker and just build directly on the images, reducing some complexity and also overhead of downloading Docker images. In addition, this commit also enables caching of the .servo and .cargo directories on Travis in an attempt to reduce build times. http://docs.travis-ci.com/user/caching/#Arbitrary-directories Source-Repo: https://github.com/servo/servo Source-Revision: 628c2a04326b27ac2743771dca52612c8ce30ad2 2015-10-16 23:09:36 +03:00			`dist: trusty`
servo: Merge #8361 - Add script to check if lockfile was changed (from Manishearth:lockfile_changed); r=frewsxcv Source-Repo: https://github.com/servo/servo Source-Revision: 60d40ed06afced66b5a76fc824132fb244265f06 2015-11-05 23:48:39 +03:00			`script:`
			`- ./mach build -d --verbose`
			`- bash etc/ci/lockfile_changed.sh`
servo: Merge #8601 - Check if MANIFEST.json changes as per #8587 (from mfeckie:feature/manifest-diff-ci-check); r=jdm Adds a script which checks if either of the MANIFEST.json files change in `test/wpt` in response to #8587 - Addresses currently incorrect MANIFEST.json - Adds checking script PR for saltfs to add to CI checks to follow (https://github.com/servo/saltfs/pull/163) https://reviewable.io/reviews/servo/servo/8601 Source-Repo: https://github.com/servo/servo Source-Revision: f2fe1171d2a4f4ae37cfa0e0e345662f68e41c5d 2015-11-21 17:43:10 +03:00			`- bash etc/ci/manifest_changed.sh`
servo: Merge #8036 - Travis CI building cleanup, enable caching (from frewsxcv:travis); r=metajack The only reason the Dockerfile was introduced is because the default machines that Travis uses are based on Ubuntu 12.04, which has some very old incompatible dependencies with Servo. Docker allowed use to use a new version of Ubuntu, allowing us to compile with ease. I just learned that they are currently beta testing 14.04 support: http://docs.travis-ci.com/user/trusty-ci-environment/ This commit updates our Travis config to remove our dependency on Docker and just build directly on the images, reducing some complexity and also overhead of downloading Docker images. In addition, this commit also enables caching of the .servo and .cargo directories on Travis in an attempt to reduce build times. http://docs.travis-ci.com/user/caching/#Arbitrary-directories Source-Repo: https://github.com/servo/servo Source-Revision: 628c2a04326b27ac2743771dca52612c8ce30ad2 2015-10-16 23:09:36 +03:00			`cache:`
			`directories:`
			`- .cargo`
			`- .servo`
servo: Merge #8366 - Add CCACHE infra and turn it on in travis (from larsbergstrom:ccache); r=frewsxcv r? @Manishearth This lets devs configure their use of CCACHE with their .servobuild file, as usual. For build environments, they can either have a .servobuild file or set the CCACHE env var to point at the ccache binary to use. It also adds support for ccache to our travis builds. Buildbot will come in a separate commit to the saltfs repo. It is expected that the various cargo makefiles will look at this variable and do the "right thing" to tell their native build to instead use ccache. e.g., https://github.com/servo/mozjs/pull/62 Source-Repo: https://github.com/servo/servo Source-Revision: d16ba51b4722a84f69976ca8679af672495248c8 2015-11-07 04:31:54 +03:00			`- $HOME/.ccache`
			`env: CCACHE=/usr/bin/ccache`
servo: Merge #8036 - Travis CI building cleanup, enable caching (from frewsxcv:travis); r=metajack The only reason the Dockerfile was introduced is because the default machines that Travis uses are based on Ubuntu 12.04, which has some very old incompatible dependencies with Servo. Docker allowed use to use a new version of Ubuntu, allowing us to compile with ease. I just learned that they are currently beta testing 14.04 support: http://docs.travis-ci.com/user/trusty-ci-environment/ This commit updates our Travis config to remove our dependency on Docker and just build directly on the images, reducing some complexity and also overhead of downloading Docker images. In addition, this commit also enables caching of the .servo and .cargo directories on Travis in an attempt to reduce build times. http://docs.travis-ci.com/user/caching/#Arbitrary-directories Source-Repo: https://github.com/servo/servo Source-Revision: 628c2a04326b27ac2743771dca52612c8ce30ad2 2015-10-16 23:09:36 +03:00			`addons:`
			`apt:`
			`packages:`
			`- cmake`
			`- freeglut3-dev`
			`- gperf`
			`- libosmesa6-dev`
			`- python-virtualenv`
			`- xorg-dev`
servo: Merge #8366 - Add CCACHE infra and turn it on in travis (from larsbergstrom:ccache); r=frewsxcv r? @Manishearth This lets devs configure their use of CCACHE with their .servobuild file, as usual. For build environments, they can either have a .servobuild file or set the CCACHE env var to point at the ccache binary to use. It also adds support for ccache to our travis builds. Buildbot will come in a separate commit to the saltfs repo. It is expected that the various cargo makefiles will look at this variable and do the "right thing" to tell their native build to instead use ccache. e.g., https://github.com/servo/mozjs/pull/62 Source-Repo: https://github.com/servo/servo Source-Revision: d16ba51b4722a84f69976ca8679af672495248c8 2015-11-07 04:31:54 +03:00			`- ccache`
servo: Merge #5213 - Check tidy in Travis file (from servo:tidy-travis); r=Ms2ger Source-Repo: https://github.com/servo/servo Source-Revision: a2ff1aae824d736922616cd8a592fd7d93361fa7 2015-03-14 15:54:48 +03:00
			`branches:`
			`only:`
servo: Merge #7915 - Build Servo on Travis (from frewsxcv:travis); r=larsbergstrom Closes #6962 Source-Repo: https://github.com/servo/servo Source-Revision: e5b46eb919461531b8bf5a79fc0c5e6e1ec94c75 2015-10-08 18:00:28 +03:00			`- master`