db9a3cbfb9
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
53 lines
1.4 KiB
YAML
53 lines
1.4 KiB
YAML
cache: cargo
|
|
before_cache:
|
|
- find ./target/debug -type f -maxdepth 1 -delete
|
|
- rm -fr ./target/debug/{deps,.fingerprint}/{*ra_*,*test*,*tools*,*gen_lsp*,*thread_worker*}
|
|
- rm -f ./target/.rustc_info.json
|
|
|
|
matrix:
|
|
include:
|
|
- os: linux
|
|
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_stript:
|
|
- 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
|