Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-08 19:04:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
540ad4129b
gecko-dev/servo/.travis.yml

42 lines
869 B
YAML
Raw Normal View History

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 12:54:48 +00: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 15:00:28 +00: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 15:17:25 +00:00
- sudo: false
servo: Merge #9649 - Refactoring tidy (from Wafflespeanut:tidy_progress); r=jdm Improved tidy's code for efficiency (which now shows progress while checking through files) Source-Repo: https://github.com/servo/servo Source-Revision: 553cf3d8e8dfc5eb1222fc48b507d6578da6bc66
2016-02-25 17:06:21 +00:00
script: ./mach test-tidy --no-progress
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 20:09:36 +00:00
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 15:17:25 +00: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 20:09:36 +00: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 20:48:39 +00:00
script:
- ./mach build -d --verbose
servo: Merge #8873 - Run unit tests in ci (from apechimp:master); r=Manishearth Fixes #8856. Source-Repo: https://github.com/servo/servo Source-Revision: a4f617bf1857ab054432251839ec6785a9f015ad
2015-12-07 19:59:18 +00:00
- ./mach test-unit
servo: Merge #9469 - Integrate compiletest_rs (from fhahn:compiletest2); r=jdm This PR integrates `compiletest_rs` as suggested in #5646. I created a new `tests/compiletest` directory which contains separate crates for the tests. Currently this PR includes `compile-fail` tests for some lints (acutally all except inheritance_integrity, beacuse I'm not sure how to include the dom stuff in a way the `#[dom_struct]` works). I gathered that there should be more crates for which compiletests make sense and would appreciate any pointers to relevant crates. Source-Repo: https://github.com/servo/servo Source-Revision: d574b78313be75f3388123d11354b897598877a3
2016-02-04 15:30:21 +00:00
- ./mach test-compiletest
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 20:48:39 +00:00
- bash etc/ci/lockfile_changed.sh
servo: Merge #9044 - Update offscreen_gl_context (from emilio:offscreen-gl-up); r=jdm cc: https://github.com/ecoal95/rust-offscreen-rendering-context/pull/46 Source-Repo: https://github.com/servo/servo Source-Revision: da8952b7023a92b7a69bd4423905594f4baa8f29
2015-12-23 15:05:37 +00: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 20:09:36 +00: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 01:31:54 +00: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 20:09:36 +00:00
addons:
apt:
packages:
- cmake
- freeglut3-dev
- gperf
- libosmesa6-dev
servo: Merge #9044 - Update offscreen_gl_context (from emilio:offscreen-gl-up); r=jdm cc: https://github.com/ecoal95/rust-offscreen-rendering-context/pull/46 Source-Repo: https://github.com/servo/servo Source-Revision: da8952b7023a92b7a69bd4423905594f4baa8f29
2015-12-23 15:05:37 +00:00
- libgles2-mesa-dev
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 20:09:36 +00:00
- 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 01:31:54 +00: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 12:54:48 +00: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 15:00:28 +00:00
- master
servo: Merge #9399 - Fixes #9398 Integrate BuildTimeTrend into TravisCI (from nxnfufunezn:build_time-9398); r=jdm r? @jdm Source-Repo: https://github.com/servo/servo Source-Revision: 0dd024e492cff1bbbbceeb295c0e220d9dd045fc
2016-01-21 21:18:01 +00:00
notifications:
webhooks:
- https://buildtimetrend.herokuapp.com/travis
Reference in New Issue Copy Permalink