extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-10-17 07:42:53 +02:00
Code Issues Packages Projects Releases Wiki Activity
b5f8f64d79
nushell/.azure/azure-pipelines.yml

67 lines
2.0 KiB
YAML
Raw Normal View History

Try to add azure pipelines
2019-06-18 06:37:47 +02:00
trigger:
Update azure-pipelines.yml
2020-07-05 22:20:38 +02:00
- main
Try to add azure pipelines
2019-06-18 06:37:47 +02:00
strategy:
matrix:
Move azure pipeline to stable
2019-11-07 18:13:39 +01:00
linux-stable:
Bump Pipeline images (#1255) * Bump Pipeline images * Update azure-pipelines.yml * Update azure-pipelines.yml
2020-01-21 22:39:31 +01:00
image: ubuntu-18.04
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
style: 'unflagged'
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
linux-minimal:
image: ubuntu-18.04
style: 'minimal'
Split extra (#2348) * Split default/extra plugins * Oops, too many deletes * Pipelines
2020-08-14 06:45:27 +02:00
linux-extra:
image: ubuntu-18.04
style: 'extra'
Add wasm sample for CI (#2372) * Add wasm sample for CI * Add wasm sample for CI * Add wasm sample for CI
2020-08-18 21:34:05 +02:00
linux-wasm:
image: ubuntu-18.04
style: 'wasm'
Move azure pipeline to stable
2019-11-07 18:13:39 +01:00
macos-stable:
ci: fix macOS agent (#4203) I noticed the agent documentation uses uppercase: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
2021-12-13 20:08:03 +01:00
image: macOS-10.14
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
style: 'unflagged'
Move azure pipeline to stable
2019-11-07 18:13:39 +01:00
windows-stable:
Bump Pipeline images (#1255) * Bump Pipeline images * Update azure-pipelines.yml * Update azure-pipelines.yml
2020-01-21 22:39:31 +01:00
image: windows-2019
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
style: 'unflagged'
fmt:
Bump Pipeline images (#1255) * Bump Pipeline images * Update azure-pipelines.yml * Update azure-pipelines.yml
2020-01-21 22:39:31 +01:00
image: ubuntu-18.04
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
style: 'fmt'
Try to add azure pipelines
2019-06-18 06:37:47 +02:00
pool:
vmImage: $(image)
steps:
- bash: |
set -e
Update azure-pipelines.yml
2019-10-02 18:27:03 +02:00
if [ -e /etc/debian_version ]
then
sudo apt-get -y install libxcb-composite0-dev libx11-dev
fi
Bump Pipeline images (#1255) * Bump Pipeline images * Update azure-pipelines.yml * Update azure-pipelines.yml
2020-01-21 22:39:31 +01:00
if [ "$(uname)" == "Darwin" ]; then
curl https://sh.rustup.rs -sSf | sh -s -- -y --no-modify-path --default-toolchain "stable"
Bump rustyline (#1644) * Bump rustyline * Fix new clippy warnings * Add pipeline command
2020-04-23 22:00:49 +02:00
echo "Installing clippy"
rustup component add clippy --toolchain stable-x86_64-apple-darwin
Bump Pipeline images (#1255) * Bump Pipeline images * Update azure-pipelines.yml * Update azure-pipelines.yml
2020-01-21 22:39:31 +01:00
export PATH=$HOME/.cargo/bin:$PATH
fi
fix the name of 'do' (#2152) * fix the name of 'do' * try to fix ci
2020-07-11 07:09:05 +02:00
# rustup update
# rustc -Vv
# echo "##vso[task.prependpath]$HOME/.cargo/bin"
# rustup component add rustfmt
Try to add azure pipelines
2019-06-18 06:37:47 +02:00
displayName: Install Rust
Split extra (#2348) * Split default/extra plugins * Oops, too many deletes * Pipelines
2020-08-14 06:45:27 +02:00
- bash: RUSTFLAGS="-D warnings" cargo test --all
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
condition: eq(variables['style'], 'unflagged')
displayName: Run tests
Fix clippy lint and disable broken lint (#3865)
2021-07-29 22:11:47 +02:00
- bash: RUSTFLAGS="-D warnings" cargo clippy --all -- -D clippy::unwrap_used -A clippy::needless_collect
Move to using clippy (#1142) * Clippy fixes * Finish converting to use clippy * fix warnings in new master * fix windows * fix windows Co-authored-by: Artem Vorotnikov <artem@vorotnikov.me>
2019-12-31 08:36:08 +01:00
condition: eq(variables['style'], 'unflagged')
displayName: Check clippy lints
Wasm fix (#3729) * Try to fix azure pipelines * Try to fix azure pipelines * Try to fix azure pipelines
2021-07-04 10:11:22 +02:00
- bash: cd samples/wasm && npm install wasm-pack && node ./node_modules/wasm-pack/run.js build
Add wasm sample for CI (#2372) * Add wasm sample for CI * Add wasm sample for CI * Add wasm sample for CI
2020-08-18 21:34:05 +02:00
condition: eq(variables['style'], 'wasm')
displayName: Wasm build
Update rustyline to latest (#2565) * Update rustyline to latest * Go ahead and use rustyline for testing
2020-09-17 08:02:30 +02:00
- bash: RUSTFLAGS="-D warnings" cargo test --all --no-default-features --features=rustyline-support
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
condition: eq(variables['style'], 'minimal')
displayName: Run tests
Split extra (#2348) * Split default/extra plugins * Oops, too many deletes * Pipelines
2020-08-14 06:45:27 +02:00
- bash: RUSTFLAGS="-D warnings" cargo test --all --features=extra
condition: eq(variables['style'], 'extra')
displayName: Run tests
install correct version
2019-09-11 19:49:16 +02:00
- bash: cargo fmt --all -- --check
Feature flagging infrastructure This commit adds the ability to work on features behind a feature flag that won't be included in normal builds of nu. These features are not exposed as Cargo features, as they reflect incomplete features that are not yet stable. To create a feature, add it to `features.toml`: ```toml [hintsv1] description = "Adding hints based on error states in the highlighter" enabled = false ``` Each feature in `features.toml` becomes a feature flag accessible to `cfg`: ```rs println!("hintsv1 is enabled"); ``` By default, features are enabled based on the value of the `enabled` field. You can also enable a feature from the command line via the `NUSHELL_ENABLE_FLAGS` environment variable: ```sh $ NUSHELL_ENABLE_FLAGS=hintsv1 cargo run ``` You can enable all flags via `NUSHELL_ENABLE_ALL_FLAGS`. This commit also updates the CI setup to run the build with all flags off and with all flags on. It also extracts the linting test into its own parallelizable test, which means it doesn't need to run together with every other test anymore. When working on a feature, you should also add tests behind the same flag. A commit is mergable if all tests pass with and without the flag, allowing incomplete commits to land on master as long as the incomplete code builds and passes tests.
2019-10-11 20:39:05 +02:00
condition: eq(variables['style'], 'fmt')
CI
2019-09-11 19:06:59 +02:00
displayName: Lint
Reference in New Issue Copy Permalink