rust/.travis.yml

cache: cargo
before_cache:
    - find ./target/debug -maxdepth 1 -type f -delete
    - rm -fr ./target/debug/{deps,.fingerprint}/{*ra_*,*test*,*gen_lsp*,*thread_worker*}
    - rm -f  ./target/.rustc_info.json

matrix:
    include:
        - os: linux
          dist: xenial
          language: rust
          rust: stable
          script:
              - rustup component add rustfmt
              - rustup component add rust-src
              - cargo test --no-run  # let's measure compile time separately
              - cargo test
          env:
              - RUSTFLAGS="-D warnings", CARGO_INCREMENTAL=0

        - os: linux
          if: branch = master AND type = push
          before_script:
              - DEPLOY_DOCS=1
          language: rust
          rust: stable
          script:
              - cargo doc --all --no-deps
          env:
              - RUSTFLAGS="-D warnings", CARGO_INCREMENTAL=0

        - language: node_js
          node_js: node
          before_script: false
          script:
              - cd editors/code && npm ci && npm run travis

branches:
    only:
        - staging
        - master
        - trying

deploy:
    provider: pages
    skip-cleanup: true
    github-token: $DOCS_TOKEN  # Set in the settings page of your repository, as a secure variable
    keep-history: true
    local-dir: target/doc
    branch: gh-pages
    on:
        branch: master
        condition: $DEPLOY_DOCS = 1
Cache caro on Travis 2018-10-15 20:01:33 +02:00			`cache: cargo`
Don't cache ever changing stuff 2018-10-20 22:33:45 +02:00			`before_cache:`
Use Xenial image and fix find call 2019-05-23 15:05:01 +02:00			`- find ./target/debug -maxdepth 1 -type f -delete`
don't remove tools from cache On CI, we remove this project's artifacts from ./target before caching it. This way, cache never changes, because it only caches deps. We do this approximatelly, and, together with our own tools crate, we also remove itertools, which are used by some other deps. Given that tools change rarely, let's just cache them? 2019-05-30 09:17:29 +02:00			`- rm -fr ./target/debug/{deps,.fingerprint}/{ra_,test,gen_lsp,thread_worker}`
Reformat .travis.yml (using the vscode prettier extension) TODO: Check this on CI. Maybe we should change the prettier script in `editors/code`, or move it to somewhere else (`tests/format` maybe) Editing the script in editors/code would be easiest as that means we don't have to double install some shared `node_modules` 2018-12-29 11:31:20 +01:00			`- rm -f ./target/.rustc_info.json`
Don't cache ever changing stuff 2018-10-20 22:33:45 +02:00
Enforce rustfmt format 2018-01-28 00:31:23 +01:00			`matrix:`
Reformat .travis.yml (using the vscode prettier extension) TODO: Check this on CI. Maybe we should change the prettier script in `editors/code`, or move it to somewhere else (`tests/format` maybe) Editing the script in editors/code would be easiest as that means we don't have to double install some shared `node_modules` 2018-12-29 11:31:20 +01:00			`include:`
			`- os: linux`
Use Xenial image and fix find call 2019-05-23 15:05:01 +02:00			`dist: xenial`
Remove windows from CI We don't actually look at the CI results for windows anyway! In general, rust-analyzer should be written in a completely OS-independent way. That is, testing on one OS should be enough. If this is not the case, that means something is seriously broken. No doubt there are components which actually talk to the outside world, and they may be platform dependent. We should extract such components to a separate repo with an extensive multi platform CI, like we did for VFS 2019-03-25 08:13:44 +01:00			`language: rust`
			`rust: stable`
			`script:`
			`- rustup component add rustfmt`
			`- rustup component add rust-src`
			`- cargo test --no-run # let's measure compile time separately`
			`- cargo test`
			`env:`
			`- RUSTFLAGS="-D warnings", CARGO_INCREMENTAL=0`

			`- os: linux`
			`if: branch = master AND type = push`
fix build 2019-03-25 08:48:24 +01:00			`before_script:`
Add docs build 2019-03-23 20:43:38 +01:00			`- DEPLOY_DOCS=1`
Remove windows from CI We don't actually look at the CI results for windows anyway! In general, rust-analyzer should be written in a completely OS-independent way. That is, testing on one OS should be enough. If this is not the case, that means something is seriously broken. No doubt there are components which actually talk to the outside world, and they may be platform dependent. We should extract such components to a separate repo with an extensive multi platform CI, like we did for VFS 2019-03-25 08:13:44 +01:00			`language: rust`
			`rust: stable`
			`script:`
			`- cargo doc --all --no-deps`
			`env:`
			`- RUSTFLAGS="-D warnings", CARGO_INCREMENTAL=0`

Reformat .travis.yml (using the vscode prettier extension) TODO: Check this on CI. Maybe we should change the prettier script in `editors/code`, or move it to somewhere else (`tests/format` maybe) Editing the script in editors/code would be easiest as that means we don't have to double install some shared `node_modules` 2018-12-29 11:31:20 +01:00			`- language: node_js`
			`node_js: node`
			`before_script: false`
			`script:`
			`- cd editors/code && npm ci && npm run travis`
The last of the Masters 2018-01-28 01:23:05 +01:00
			`branches:`
Reformat .travis.yml (using the vscode prettier extension) TODO: Check this on CI. Maybe we should change the prettier script in `editors/code`, or move it to somewhere else (`tests/format` maybe) Editing the script in editors/code would be easiest as that means we don't have to double install some shared `node_modules` 2018-12-29 11:31:20 +01:00			`only:`
			`- staging`
			`- master`
			`- trying`
Add docs build 2019-03-23 20:43:38 +01:00
			`deploy:`
			`provider: pages`
			`skip-cleanup: true`
			`github-token: $DOCS_TOKEN # Set in the settings page of your repository, as a secure variable`
			`keep-history: true`
			`local-dir: target/doc`
			`branch: gh-pages`
			`on:`
			`branch: master`
			`condition: $DEPLOY_DOCS = 1`