about summary refs log tree commit diff
path: root/src/ci/azure-pipelines
AgeCommit message (Collapse)AuthorLines
2019-10-25ci: split install-msys2 step into two separate scriptsPietro Albini-0/+7
2019-10-25ci: extract verifying line endings into a scriptPietro Albini-21/+5
2019-10-25ci: extract checking out submodules into a scriptPietro Albini-11/+5
2019-10-25ci: extract enabling ipv6 on docker into a scriptPietro Albini-9/+5
2019-10-25ci: extract installing ninja into a scriptPietro Albini-14/+5
2019-10-25ci: extract installing mingw into a scriptPietro Albini-40/+7
2019-10-25ci: extract installing msys2 into a scriptPietro Albini-52/+7
2019-10-25ci: extract disabling git crlf handling into a scriptPietro Albini-5/+7
2019-10-25ci: extract parts of windows-build-deps into scriptsPietro Albini-35/+18
2019-10-25ci: extract switching xcode into a scriptPietro Albini-8/+5
2019-10-25ci: extract installing clang into a scriptPietro Albini-47/+5
2019-10-25ci: extract installing sccache into a scriptPietro Albini-22/+6
2019-10-25ci: extract dumping the environment into a scriptPietro Albini-10/+2
2019-10-25ci: move install-awscli.sh into scripts/Pietro Albini-1/+1
2019-10-24workaround msys2 bugMateusz Mikuła-0/+23
Co-Authored-By: Pietro Albini <pietro@pietroalbini.org>
2019-10-16Remove PR runs, enable wasm32 CI, and move asmjs to disabledThomas Lively-6/+2
2019-10-16Temporarily enable asmjs and wasm32 on PR CIThomas Lively-0/+4
2019-09-20Auto merge of #64553 - alexcrichton:windows-bash-install-scripts, ↵bors-38/+39
r=Mark-Simulacrum 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. Closes #64551
2019-09-19azure: Convert Windows installations scripts to `bash`Alex Crichton-38/+39
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.
2019-09-19ci: split aws credentials in two separate users with scoped permsPietro Albini-7/+10
This commit changes our CI to use two separate IAM users to authenticate with AWS: * ci--rust-lang--rust--sccache: has access to the rust-lang-ci-sccache2 S3 bucket and its credentials are available during the whole build. * ci--rust-lang--rust--upload: has access to the rust-lang-ci2 S3 bucket and its credentials are available just during the upload step. The new tokens are available in the `prod-credentials` library.
2019-09-17Auto merge of #64517 - alexcrichton:less-assertions, r=pietroalbinibors-0/+9
azure: Disable more LLVM/debug assertions in This commit disables LLVM/debug assertions in our 5 slowest builders: * i686-gnu * i686-gnu-nopt * i686-msvc-1 * i686-msvc-2 * x86_64-msvc-cargo This is reducing the amount of test coverage for LLVM/debug assertions, but we're just unfortunately running out of time on CI too many times. Some test builds have shown that i686-gnu drops nearly an hour of CI time by disabling these two assertions. Perhaps when we eventually get 4-core machines we can reenable these, but for now turn them off and hook them up to the tracking issue at #59637 which will ideally be repurposes to tracking all of these.
2019-09-16azure: Disable more LLVM/debug assertions inAlex Crichton-0/+9
This commit disables LLVM/debug assertions in our 5 slowest builders: * i686-gnu * i686-gnu-nopt * i686-msvc-1 * i686-msvc-2 * x86_64-msvc-cargo This is reducing the amount of test coverage for LLVM/debug assertions, but we're just unfortunately running out of time on CI too many times. Some test builds have shown that i686-gnu drops nearly an hour of CI time by disabling these two assertions. Perhaps when we eventually get 4-core machines we can reenable these, but for now turn them off and hook them up to the tracking issue at #59637 which will ideally be repurposes to tracking all of these.
2019-09-16ci: ensure all tool maintainers are assignable on issuesPietro Albini-0/+7
GitHub only allows people explicitly listed as collaborators on the repository or who commented on the issue/PR to be assignees, failing to create the issue if non-assignable people are assigned. This adds an extra check on CI to make sure all the people listed as tool maintainers can be assigned to toolstate issues. The check won't be executed on PR builds due to the lack of a valid token.
2019-08-16Rollup merge of #63636 - pietroalbini:ci-mingw, r=alexcrichtonMazdak Farrokhzad-4/+4
ci: move linkcheck from mingw-2 to mingw-1 Running UI tests now takes a huge amount of time on mingw builders (between 40 and 50 minutes), with mingw-1 builders taking even an hour less to finish than mingw-2. This PR moves linkcheck from mingw-2 to mingw-1, removing between 10 and 20 minutes of runtime on the -2 builders. r? @alexcrichton
2019-08-16ci: move linkcheck from mingw-2 to mingw-1Pietro Albini-4/+4
Running UI tests now takes a huge amount of time on mingw builders (between 40 and 50 minutes), with mingw-1 builders taking even an hour less to finish than mingw-2. This PR moves linkcheck from mingw-2 to mingw-1, removing between 10 and 20 minutes of runtime on the -2 builders.
2019-08-16ci: properly set the job name in CPU statsPietro Albini-1/+1
2019-08-12ci: move mirrors to their standalone bucketPietro Albini-12/+12
Currently mirrors are stored in the rust-lang-ci2 S3 bucket along with CI toolchains. This is problematic for multiple reasons: - CI IAM credentials are allowed to both edit and delete those files. A malicious user gaining access to those credentials would be able to change our mirrored dependencies, possibly backdooring the compiler. - Contents of the rust-lang-ci2 bucket are disposable except for the mirrors' content. When we implement backups for S3 buckets we'd have to replicate just that part of the bucket, complicating the backup logic and increasing the chance of mistakes. A standalone bucket will be way easier to backup. This commit switches our CI to use the new rust-lang-ci-mirrors bucket.
2019-08-08remove test-miri flag from bootstrapRalf Jung-1/+1
2019-08-03ci: move .azure-pipelines to src/ci/azure-pipelinesPietro Albini-0/+881