diff options
| author | Alex Crichton <alex@alexcrichton.com> | 2019-09-17 07:40:27 -0700 |
|---|---|---|
| committer | Alex Crichton <alex@alexcrichton.com> | 2019-09-19 07:29:45 -0700 |
| commit | 72ea960056d40f1fcb5efb42d5914b35f908f63e (patch) | |
| tree | 128de0a9f3f28aaeb007111074321fccb1c2409b /src/libsyntax/parse/parser | |
| parent | 7ac21e7636f7b3c0eb3e31b13c7087b4de7aa5a9 (diff) | |
| download | rust-72ea960056d40f1fcb5efb42d5914b35f908f63e.tar.gz rust-72ea960056d40f1fcb5efb42d5914b35f908f63e.zip | |
azure: Convert Windows installations scripts to `bash`
Looks like `script`, which uses `cmd.exe`, doesn't have fail-fast behavior and if a leading command fails the script doesn't actually fail so long as the last command succeeds. We instead want the opposite behavior where if any step fails the whole script fails. I don't really know `cmd.exe` that well, nor powershell, so I've opted to move everything to `bash` which should be a good common denominator amongst all platforms to work with. Additionally I know that `set -e` works to cause scripts to fail fast. Note that some scripts remain as `script` since they don't appear to work in` bash`. I'm not really sure why but I reorganized them slightly to have the "meaty command" run at the end.
Diffstat (limited to 'src/libsyntax/parse/parser')
0 files changed, 0 insertions, 0 deletions
