serde/.travis.yml

sudo: false
language: rust
cache: cargo

# run builds for all the trains (and more)
rust:
  - stable
  - beta
  - nightly
  - 1.13.0
  - 1.15.0
  - 1.20.0
  - 1.21.0
  - 1.25.0
  - 1.26.0

matrix:
  include:
    - rust: nightly
      env: CLIPPY=true
    - rust: nightly
      env: EMSCRIPTEN=true
      script: nvm install 9 && ./travis.sh

script: ./travis.sh
Remove some low-risk travis builds 2016-06-11 18:18:30 -05:00			`sudo: false`
initial travis version 2014-09-07 03:27:03 -05:00			`language: rust`
move to cargo clippy instead of using the clippy plugin (#733) * move to cargo clippy instead of using the clippy plugin fixes #729 * non-exectable scripts must be run with `sh` * don't build serde in the clippy travis job * only run clippy tests if installing clippy succeeds * why is travis so picky? * no more serde_codegen * serde_test_suite_deps has no features * don't use empty loops, llvm optimizes them to undefined behaviour * abort the clippy job when clippy lints are triggered * use caches on travis to speed up builds * why are we even using `travis-cargo`? * need to reinstall clippy frequently due to nightly updates * command line tools are hard 2017-01-31 11:09:37 -06:00			`cache: cargo`
Indent the travis config to look like serde_json's 2017-01-27 16:17:07 -06:00
			`# run builds for all the trains (and more)`
Travis work 2015-05-21 00:44:50 -05:00			`rust:`
Indent the travis config to look like serde_json's 2017-01-27 16:17:07 -06:00			`- stable`
			`- beta`
			`- nightly`
CI builders for all versions mentioned in the build script This should prevent accidentally inserting something under one of these cfgs that is available only on a newer rustc. For example if something is changed in the Duration serialization, but that change works only on a recent rustc, our test suite will not have caught it before. 2018-06-03 03:26:51 -05:00			`- 1.13.0`
			`- 1.15.0`
			`- 1.20.0`
			`- 1.21.0`
			`- 1.25.0`
			`- 1.26.0`
Indent the travis config to look like serde_json's 2017-01-27 16:17:07 -06:00
move to cargo clippy instead of using the clippy plugin (#733) * move to cargo clippy instead of using the clippy plugin fixes #729 * non-exectable scripts must be run with `sh` * don't build serde in the clippy travis job * only run clippy tests if installing clippy succeeds * why is travis so picky? * no more serde_codegen * serde_test_suite_deps has no features * don't use empty loops, llvm optimizes them to undefined behaviour * abort the clippy job when clippy lints are triggered * use caches on travis to speed up builds * why are we even using `travis-cargo`? * need to reinstall clippy frequently due to nightly updates * command line tools are hard 2017-01-31 11:09:37 -06:00			`matrix:`
			`include:`
			`- rust: nightly`
			`env: CLIPPY=true`
Add Emscripten build in Travis 2018-09-02 14:34:13 -05:00			`- rust: nightly`
			`env: EMSCRIPTEN=true`
Nvm install in .travis.yml The one in travis.sh was failing: ./travis.sh: line 56: nvm: command not found The command "./travis.sh" exited with 127. 2018-09-02 14:45:10 -05:00			`script: nvm install 9 && ./travis.sh`
move to cargo clippy instead of using the clippy plugin (#733) * move to cargo clippy instead of using the clippy plugin fixes #729 * non-exectable scripts must be run with `sh` * don't build serde in the clippy travis job * only run clippy tests if installing clippy succeeds * why is travis so picky? * no more serde_codegen * serde_test_suite_deps has no features * don't use empty loops, llvm optimizes them to undefined behaviour * abort the clippy job when clippy lints are triggered * use caches on travis to speed up builds * why are we even using `travis-cargo`? * need to reinstall clippy frequently due to nightly updates * command line tools are hard 2017-01-31 11:09:37 -06:00
Allow running travis build locally 2017-01-31 11:17:33 -06:00			`script: ./travis.sh`