mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
826a8ef52e
rust/.github/workflows/ci.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

726 lines
29 KiB
YAML
Raw Normal View History

ci: add github actions configuration
2019-11-26 05:06:30 -06:00
#############################################################
# WARNING: automatically generated file, DO NOT CHANGE! #
#############################################################
# This file was automatically generated by the expand-yaml-anchors tool. The
# source file that generated this one is:
#
# src/ci/github-actions/ci.yml
#
# Once you make changes to that file you need to run:
#
# ./x.py run src/tools/expand-yaml-anchors/
#
# The CI build will fail if the tool is not run after changes to this file.
---
name: CI
"on":
push:
branches:
- auto
- try
Enable perf try builder This adds a dedicated branch for perf to use for CI, intended to allow perf to enqueue builds without needing to use bors. bors is great, but bors requires an open PR to work, and we want to invoke perf on closed PRs sometimes (in particular, rollups).
2020-07-21 13:53:39 -05:00
- try-perf
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- master
pull_request:
branches:
- "**"
Update ci.yml Signed-off-by: sashashura <93376818+sashashura@users.noreply.github.com>
2022-09-02 11:37:17 -05:00
permissions:
contents: read
ci: set a default shell on GHA
2020-04-22 11:53:11 -05:00
defaults:
run:
ci: Replace exec-with-shell wrapper with "plain bash" Also, promote defaults.run.shell from inside only the primary jobs to the top level. The src/ci/exec-with-shell.py wrapper script was formerly used to change out the shell mid-job by intercepting a CI_OVERRIDE_SHELL environment variable. Now, instead, we just set `bash` as the global default across all jobs, and we also delete the exec-with-shell.py script. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
2020-07-17 08:44:14 -05:00
shell: bash
Cancel in-progress workflow runs after a push
2023-06-23 04:22:23 -05:00
concurrency:
CI: include workflow name in concurrency group Currently, this won't change anything, because we only have one relevant workflow (`CI`), but for future proofing we should probably include the workflow name in the concurrency group.
2023-06-29 17:08:38 -05:00
group: "${{ github.workflow }}-${{ ((github.ref == 'refs/heads/try' || github.ref == 'refs/heads/try-perf') && github.sha) || github.ref }}"
Cancel in-progress workflow runs after a push
2023-06-23 04:22:23 -05:00
cancel-in-progress: true
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
jobs:
pr:
Improve job names in Github Actions preview Before: `CI / PR (mingw-check, false, ubuntu-20.04-16core-64gb) (pull_request)` After: `CI / PR - mingw-check (pull_request)`
2023-04-02 16:48:12 -05:00
name: "PR - ${{ matrix.name }}"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
CI: merge x86_64-gnu-llvm-14 and x86_64-gnu-llvm-14-stage1 CI jobs
2023-06-18 17:02:45 -05:00
PR_CI_JOB: 1
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
CI_JOB_NAME: "${{ matrix.name }}"
Enable Cargo's sparse protocol in CI
2023-01-31 20:13:57 -06:00
CARGO_REGISTRIES_CRATES_IO_PROTOCOL: sparse
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
HEAD_SHA: "${{ github.event.pull_request.head.sha || github.sha }}"
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
SCCACHE_BUCKET: rust-lang-ci-sccache2
TOOLSTATE_REPO: "https://github.com/rust-lang-nursery/rust-toolstate"
CACHE_DOMAIN: ci-caches.rust-lang.org
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
if: "github.event_name == 'pull_request'"
Remove `tidy` key in PR CI This avoids confusing error messages when adding an `auto` job to CI (as recommended in the dev-guide: https://rustc-dev-guide.rust-lang.org/tests/ci.html#using-ci-to-test).
2023-05-04 17:42:44 -05:00
continue-on-error: "${{ matrix.name == 'mingw-check-tidy' }}"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
strategy:
matrix:
include:
- name: mingw-check
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
Run `tidy` in its own job in PR CI This duplicates mingw-check into two jobs where one job runs `tidy` only while the other job does not. The tidy job will not cancel other jobs on failure.
2022-12-22 09:47:14 -06:00
env: {}
- name: mingw-check-tidy
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
Update the minimum external LLVM to 15
2023-07-27 16:07:08 -05:00
- name: x86_64-gnu-llvm-15
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: x86_64-gnu-tools
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
Run the tools builder on all PRs Previously, it would only run on changes to subtrees, submodules, or select directories. That made it so that changes to the compiler that broke tools would only be detected on a full bors merge. This makes it so the tools builder runs by default, making it easier to catch breaking changes to clippy (which was the most effected).
2023-02-05 13:53:39 -06:00
env: {}
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
timeout-minutes: 600
runs-on: "${{ matrix.os }}"
steps:
- name: disable git crlf conversion
run: git config --global core.autocrlf false
- name: checkout the source code
update: actions/checkout@v2 to actions/checkout@v3 update: actions/checkout@v2 to actions/checkout@v3 for all yaml files Revert "update: actions/checkout@v2 to actions/checkout@v3 for all yaml files" This reverts commit 7445e582b900f0f56f5f2bd9036aacab97ef28e9. change GitHub Actions version v2 to v3 change GitHub Actions
2022-04-14 00:37:41 -05:00
uses: actions/checkout@v3
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
with:
fetch-depth: 2
ci: allow RLA to pick the right PR number
2020-07-20 10:11:30 -05:00
- name: configure the PR in which the error message will be posted
run: "echo \"[CI_PR_NUMBER=$num]\""
env:
num: "${{ github.event.number }}"
fix env var name
2021-02-25 20:41:25 -06:00
if: "success() && !env.SKIP_JOB && github.event_name == 'pull_request'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: add extra environment variables
run: src/ci/scripts/setup-environment.sh
env:
EXTRA_VARIABLES: "${{ toJson(matrix.env) }}"
if: success() && !env.SKIP_JOB
- name: decide whether to skip this job
run: src/ci/scripts/should-skip-this.sh
if: success() && !env.SKIP_JOB
ci: error out if someone sends a PR to the wrong branch
2021-05-06 11:47:37 -05:00
- name: ensure the channel matches the target branch
run: src/ci/scripts/verify-channel.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: collect CPU statistics
run: src/ci/scripts/collect-cpu-stats.sh
if: success() && !env.SKIP_JOB
- name: show the current environment
run: src/ci/scripts/dump-environment.sh
if: success() && !env.SKIP_JOB
- name: install sccache
run: src/ci/scripts/install-sccache.sh
if: success() && !env.SKIP_JOB
Bring back XCode selection CI script This reverts commit 8514b0097b28f84ee5cfead059a5771c6a693fb0.
2022-11-19 14:18:09 -06:00
- name: select Xcode
run: src/ci/scripts/select-xcode.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: install clang
run: src/ci/scripts/install-clang.sh
if: success() && !env.SKIP_JOB
- name: install WIX
run: src/ci/scripts/install-wix.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
Move submodule checkout before msys2 installation. For some reason, `tar` behaves differently in such a way that it does not create symlinks on Windows correctly, resulting in `Cannot create symlink to 'ld.gold': No such file or directory` errors.
2022-03-01 12:16:47 -06:00
- name: checkout submodules
run: src/ci/scripts/checkout-submodules.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: install MSYS2
run: src/ci/scripts/install-msys2.sh
if: success() && !env.SKIP_JOB
- name: install MinGW
run: src/ci/scripts/install-mingw.sh
if: success() && !env.SKIP_JOB
- name: install ninja
run: src/ci/scripts/install-ninja.sh
if: success() && !env.SKIP_JOB
- name: enable ipv6 on Docker
run: src/ci/scripts/enable-docker-ipv6.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
- name: ensure line endings are correct
run: src/ci/scripts/verify-line-endings.sh
if: success() && !env.SKIP_JOB
CI: Verify commits in beta & stable are in upstream branches. Closes #74721
2021-07-29 12:00:13 -05:00
- name: ensure backported commits are in upstream branches
run: src/ci/scripts/verify-backported-commits.sh
if: success() && !env.SKIP_JOB
add script to prevent point releases with same number as existing ones
2022-01-20 14:18:04 -06:00
- name: ensure the stable version number is correct
run: src/ci/scripts/verify-stable-version-number.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: run the build
run: src/ci/scripts/run-build-from-ci.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.CACHES_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.CACHES_AWS_ACCESS_KEY_ID)] }}"
TOOLSTATE_REPO_ACCESS_TOKEN: "${{ secrets.TOOLSTATE_REPO_ACCESS_TOKEN }}"
if: success() && !env.SKIP_JOB
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
- name: create github artifacts
run: src/ci/scripts/create-doc-artifacts.sh
if: success() && !env.SKIP_JOB
- name: upload artifacts to github
uses: actions/upload-artifact@v3
with:
name: "${{ env.DOC_ARTIFACT_NAME }}"
path: obj/artifacts/doc
if-no-files-found: ignore
retention-days: 5
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: upload artifacts to S3
run: src/ci/scripts/upload-artifacts.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.ARTIFACTS_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.ARTIFACTS_AWS_ACCESS_KEY_ID)] }}"
if: "success() && !env.SKIP_JOB && (github.event_name == 'push' || env.DEPLOY == '1' || env.DEPLOY_ALT == '1')"
auto:
Improve job names in Github Actions preview Before: `CI / PR (mingw-check, false, ubuntu-20.04-16core-64gb) (pull_request)` After: `CI / PR - mingw-check (pull_request)`
2023-04-02 16:48:12 -05:00
name: "auto - ${{ matrix.name }}"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
CI_JOB_NAME: "${{ matrix.name }}"
Enable Cargo's sparse protocol in CI
2023-01-31 20:13:57 -06:00
CARGO_REGISTRIES_CRATES_IO_PROTOCOL: sparse
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
HEAD_SHA: "${{ github.event.pull_request.head.sha || github.sha }}"
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
SCCACHE_BUCKET: rust-lang-ci-sccache2
DEPLOY_BUCKET: rust-lang-ci2
TOOLSTATE_REPO: "https://github.com/rust-lang-nursery/rust-toolstate"
TOOLSTATE_ISSUES_API_URL: "https://api.github.com/repos/rust-lang/rust/issues"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
TOOLSTATE_PUBLISH: 1
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
CACHES_AWS_ACCESS_KEY_ID: AKIA46X5W6CZI5DHEBFL
ARTIFACTS_AWS_ACCESS_KEY_ID: AKIA46X5W6CZN24CBO55
Set the AWS region.
2023-04-30 15:23:48 -05:00
AWS_REGION: us-west-1
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
CACHE_DOMAIN: ci-caches.rust-lang.org
ci: run gha workflows for try, auto and master on the fork
2020-03-20 10:46:45 -05:00
if: "github.event_name == 'push' && github.ref == 'refs/heads/auto' && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
strategy:
matrix:
include:
ci: gate on aarch64-gnu passing tests
2020-10-22 05:06:12 -05:00
- name: aarch64-gnu
os:
- self-hosted
- ARM64
- linux
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: arm-android
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: armhf-gnu
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-aarch64-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-android
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-arm-linux
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-armhf-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-armv7-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-i586-gnu-i586-i686-musl
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-i686-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
ci: Add support for dist-loongarch64-linux Co-Authored-By: YANG Xiaojuan <yangxiaojuan@loongson.cn>
2022-12-29 01:09:30 -06:00
- name: dist-loongarch64-linux
os: ubuntu-20.04-8core-32gb
env: {}
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-powerpc-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-powerpc64-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-powerpc64le-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
RISC-V GNU/Linux as host platform
2019-11-30 06:47:59 -06:00
- name: dist-riscv64-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-s390x-linux
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-various-1
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-various-2
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-x86_64-freebsd
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
build dist for x86_64-unknown-illumos This change creates a new Docker image, "dist-x86_64-illumos", and sets things up to build the full set of "dist" packages for illumos hosts, so that illumos users can use "rustup" to install packages. It also adjusts the manifest builder to expect complete toolchains for this platform.
2020-07-08 18:39:09 -05:00
- name: dist-x86_64-illumos
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
build dist for x86_64-unknown-illumos This change creates a new Docker image, "dist-x86_64-illumos", and sets things up to build the full set of "dist" packages for illumos hosts, so that illumos users can use "rustup" to install packages. It also adjusts the manifest builder to expect complete toolchains for this platform.
2020-07-08 18:39:09 -05:00
env: {}
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-x86_64-linux
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-x86_64-linux-alt
env:
IMAGE: dist-x86_64-linux
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-x86_64-musl
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: dist-x86_64-netbsd
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: i686-gnu
Downsize builders for i686-gnu The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for the `i686-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:08:01 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: i686-gnu-nopt
Downsize builders for i686-gnu The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for the `i686-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:08:01 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: mingw-check
Downsize builder for mingw-check The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builder for the `mingw-check` target have used much less resources than allocated in the past, so we are testing a smaller builder size for it.
2023-04-26 09:40:12 -05:00
os: ubuntu-20.04-4core-16gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: test-various
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: wasm32
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: x86_64-gnu
Downsize builders for some x86_64-gnu targets The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for some of the `x86_64-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:52:39 -05:00
os: ubuntu-20.04-4core-16gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
add the x86_64-gnu-stable job to test with stable channel During the 1.52 release process we had to deal with some commits that passed the test suite on the nightly branch but failed on the beta or stable branch. In that case it was due to some UI tests including the channel name in the output, but other changes might also be dependent on the channel. This commit adds a new CI job that runs the Linux x86_64 test suite with the stable branch, ensuring nightly changes also work as stable.
2021-06-07 08:01:50 -05:00
- name: x86_64-gnu-stable
env:
IMAGE: x86_64-gnu
RUST_CI_OVERRIDE_RELEASE_CHANNEL: stable
add CI_ONLY_WHEN_CHANNEL and run x86_64-gnu-stable only on nightly
2021-07-28 08:18:18 -05:00
CI_ONLY_WHEN_CHANNEL: nightly
Downsize builders for some x86_64-gnu targets The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for some of the `x86_64-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:52:39 -05:00
os: ubuntu-20.04-4core-16gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: x86_64-gnu-aux
Downsize builders for some x86_64-gnu targets The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for some of the `x86_64-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:52:39 -05:00
os: ubuntu-20.04-4core-16gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: x86_64-gnu-debug
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: x86_64-gnu-distcheck
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
ci: add a runner for vanilla LLVM 16 Like #107044, this will let us track compatibility with LLVM 16 going forward, especially after we eventually upgrade our own to the next. This also drops `tidy` here and in `x86_64-gnu-llvm-15`, syncing with that change in #106085.
2023-04-10 18:45:31 -05:00
- name: x86_64-gnu-llvm-16
env:
RUST_BACKTRACE: 1
os: ubuntu-20.04-8core-32gb
ci: add runners for vanilla LLVM 14 and 15
2023-01-18 13:14:40 -06:00
- name: x86_64-gnu-llvm-15
env:
RUST_BACKTRACE: 1
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: x86_64-gnu-nopt
Downsize builders for some x86_64-gnu targets The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for some of the `x86_64-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26 09:52:39 -05:00
os: ubuntu-20.04-4core-16gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env: {}
- name: x86_64-gnu-tools
env:
DEPLOY_TOOLSTATES_JSON: toolstates-linux.json
Trim down core counts for fast builders These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-10 07:36:45 -05:00
os: ubuntu-20.04-8core-32gb
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
- name: dist-x86_64-apple
env:
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: "./x.py dist bootstrap --include-default-paths --host=x86_64-apple-darwin --target=x86_64-apple-darwin"
Re-enable ThinLTO for rustc on x86_64-apple-darwin dist builds This reverts commit ddb6fe2e1d270d23ec09c2cb435c22229830e97c.
2022-12-17 15:55:08 -06:00
RUST_CONFIGURE_ARGS: "--enable-full-tools --enable-sanitizers --enable-profiler --set rust.jemalloc --set llvm.ninja=false --set rust.lto=thin"
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
MACOSX_DEPLOYMENT_TARGET: 10.7
Use XCode 13.4 everywhere in dist CI Do this because XCode 14 no longer supports a macOS deployment target of anything before 10.13. We need 10.7+(-ish, really 10.9+) for now.
2022-11-19 14:23:22 -06:00
SELECT_XCODE: /Applications/Xcode_13.4.1.app
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
CI: Enable overflow checks for test (non-dist) builds
2021-10-11 12:38:15 -05:00
NO_OVERFLOW_CHECKS: 1
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
DIST_REQUIRE_ALL_TOOLS: 1
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
Move target-only apple targets to separate builder
2022-01-28 11:26:36 -06:00
- name: dist-apple-various
env:
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: "./x.py dist bootstrap --include-default-paths --host='' --target=aarch64-apple-ios,x86_64-apple-ios,aarch64-apple-ios-sim"
Move target-only apple targets to separate builder
2022-01-28 11:26:36 -06:00
RUST_CONFIGURE_ARGS: "--enable-sanitizers --enable-profiler --set rust.jemalloc --set llvm.ninja=false"
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
MACOSX_DEPLOYMENT_TARGET: 10.7
Use XCode 13.4 everywhere in dist CI Do this because XCode 14 no longer supports a macOS deployment target of anything before 10.13. We need 10.7+(-ish, really 10.9+) for now.
2022-11-19 14:23:22 -06:00
SELECT_XCODE: /Applications/Xcode_13.4.1.app
Move target-only apple targets to separate builder
2022-01-28 11:26:36 -06:00
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
NO_OVERFLOW_CHECKS: 1
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
- name: dist-x86_64-apple-alt
env:
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: "./x.py dist bootstrap --include-default-paths"
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
RUST_CONFIGURE_ARGS: "--enable-extended --enable-profiler --set rust.jemalloc --set llvm.ninja=false"
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
MACOSX_DEPLOYMENT_TARGET: 10.7
Use XCode 13.4 everywhere in dist CI Do this because XCode 14 no longer supports a macOS deployment target of anything before 10.13. We need 10.7+(-ish, really 10.9+) for now.
2022-11-19 14:23:22 -06:00
SELECT_XCODE: /Applications/Xcode_13.4.1.app
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
CI: Enable overflow checks for test (non-dist) builds
2021-10-11 12:38:15 -05:00
NO_OVERFLOW_CHECKS: 1
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
Split x86_64 apple builder into two
2022-02-10 10:39:02 -06:00
- name: x86_64-apple-1
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
env:
Change `src/test` to `tests` in source files, fix tidy and tests
2023-01-05 02:45:44 -06:00
SCRIPT: "./x.py --stage 2 test --exclude tests/ui --exclude tests/rustdoc --exclude tests/run-make-fulldeps"
Split x86_64 apple builder into two
2022-02-10 10:39:02 -06:00
RUST_CONFIGURE_ARGS: "--build=x86_64-apple-darwin --enable-sanitizers --enable-profiler --set rust.jemalloc --set llvm.ninja=false"
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
MACOSX_DEPLOYMENT_TARGET: 10.8
MACOSX_STD_DEPLOYMENT_TARGET: 10.7
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
NO_OVERFLOW_CHECKS: 1
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
Split x86_64 apple builder into two
2022-02-10 10:39:02 -06:00
- name: x86_64-apple-2
env:
Change `src/test` to `tests` in source files, fix tidy and tests
2023-01-05 02:45:44 -06:00
SCRIPT: "./x.py --stage 2 test tests/ui tests/rustdoc tests/run-make-fulldeps"
ci: gate macOS on GHA too
2020-09-15 14:56:07 -05:00
RUST_CONFIGURE_ARGS: "--build=x86_64-apple-darwin --enable-sanitizers --enable-profiler --set rust.jemalloc --set llvm.ninja=false"
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
MACOSX_DEPLOYMENT_TARGET: 10.8
MACOSX_STD_DEPLOYMENT_TARGET: 10.7
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
CI: Enable overflow checks for test (non-dist) builds
2021-10-11 12:38:15 -05:00
NO_OVERFLOW_CHECKS: 1
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
Add a cross-compiling aarch64-apple-darwin CI builder
2020-08-27 12:51:33 -05:00
- name: dist-aarch64-apple
env:
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: "./x.py dist bootstrap --include-default-paths --stage 2"
Disable docs on aarch64-apple-darwin. This builder is the slowest in the fleet. This should cut a considerable amount of time. The manifest should now include the docs from x86_64-apple-darwin. Although those docs are slightly different, it should be close enough. When aarch64-apple-darwin heads towards tier 1, we can revisit whether or not to re-enable the docs.
2022-01-17 22:18:56 -06:00
RUST_CONFIGURE_ARGS: "--build=x86_64-apple-darwin --host=aarch64-apple-darwin --target=aarch64-apple-darwin --enable-full-tools --enable-sanitizers --enable-profiler --disable-docs --set rust.jemalloc --set llvm.ninja=false"
Add a cross-compiling aarch64-apple-darwin CI builder
2020-08-27 12:51:33 -05:00
RUSTC_RETRY_LINKER_ON_SEGFAULT: 1
Use XCode 13.4 everywhere in dist CI Do this because XCode 14 no longer supports a macOS deployment target of anything before 10.13. We need 10.7+(-ish, really 10.9+) for now.
2022-11-19 14:23:22 -06:00
SELECT_XCODE: /Applications/Xcode_13.4.1.app
Add a cross-compiling aarch64-apple-darwin CI builder
2020-08-27 12:51:33 -05:00
USE_XCODE_CLANG: 1
MACOSX_DEPLOYMENT_TARGET: 11.0
MACOSX_STD_DEPLOYMENT_TARGET: 11.0
NO_LLVM_ASSERTIONS: 1
NO_DEBUG_ASSERTIONS: 1
CI: Enable overflow checks for test (non-dist) builds
2021-10-11 12:38:15 -05:00
NO_OVERFLOW_CHECKS: 1
Enable building Cargo for aarch64-apple-darwin
2020-09-26 08:42:04 -05:00
DIST_REQUIRE_ALL_TOOLS: 1
Configure jemalloc for cross-compilation to aarch64-apple-darwin
2020-09-27 12:27:29 -05:00
JEMALLOC_SYS_WITH_LG_PAGE: 14
CI: use `macos-13` runner for Apple jobs
2023-07-10 13:22:15 -05:00
os: macos-13
Merge `msvc-1/2` CI jobs
2023-06-14 16:07:49 -05:00
- name: x86_64-msvc
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-msvc --enable-profiler"
Merge `msvc-1/2` CI jobs
2023-06-14 16:07:49 -05:00
SCRIPT: make ci-msvc
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
Merge `msvc-1/2` CI jobs
2023-06-14 16:07:49 -05:00
- name: i686-msvc
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
RUST_CONFIGURE_ARGS: "--build=i686-pc-windows-msvc"
Merge `msvc-1/2` CI jobs
2023-06-14 16:07:49 -05:00
SCRIPT: make ci-msvc
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
CI: merge `x86_64-msvc-cargo` and `x86_64-msvc-tools` jobs
2023-06-19 08:58:12 -05:00
- name: x86_64-msvc-ext
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
CI: merge `x86_64-msvc-cargo` and `x86_64-msvc-tools` jobs
2023-06-19 08:58:12 -05:00
SCRIPT: python x.py --stage 2 test src/tools/cargotest src/tools/cargo && src/ci/docker/host-x86_64/x86_64-gnu-tools/checktools.sh x.py /tmp/toolstate/toolstates.json windows
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-msvc --enable-lld --save-toolstates=/tmp/toolstate/toolstates.json"
Don't release Miri if its tests only failed on Windows
2021-02-02 10:33:42 -06:00
DEPLOY_TOOLSTATES_JSON: toolstates-windows.json
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
Merge `mingw-1/2` CI jobs
2023-06-15 01:49:51 -05:00
- name: i686-mingw
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
Upgrade mingw-w64 on CI
2022-08-05 14:08:53 -05:00
RUST_CONFIGURE_ARGS: "--build=i686-pc-windows-gnu"
Merge `mingw-1/2` CI jobs
2023-06-15 01:49:51 -05:00
SCRIPT: make ci-mingw
Enable downloading prebuilt LLVM in test builders See comment added for details on the test builder restriction. This is primarily intended for macOS CI, but is likely to be a slight win on other builders too.
2022-07-31 16:45:15 -05:00
NO_DOWNLOAD_CI_LLVM: 1
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
CUSTOM_MINGW: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
Merge `mingw-1/2` CI jobs
2023-06-15 01:49:51 -05:00
- name: x86_64-mingw
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
Merge `mingw-1/2` CI jobs
2023-06-15 01:49:51 -05:00
SCRIPT: make ci-mingw
Upgrade mingw-w64 on CI
2022-08-05 14:08:53 -05:00
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-gnu --enable-profiler"
Enable downloading prebuilt LLVM in test builders See comment added for details on the test builder restriction. This is primarily intended for macOS CI, but is likely to be a slight win on other builders too.
2022-07-31 16:45:15 -05:00
NO_DOWNLOAD_CI_LLVM: 1
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
CUSTOM_MINGW: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-x86_64-msvc
env:
Revert "enable ThinLTO for rustc on x86_64-pc-windows-msvc dist builds" This lead to a miscompilation in at least `char::is_whitespace` and probably in more unknown places..... This reverts commit 684663ed380d0e6a6e135aed9c6055ab4ba94ac8.
2023-03-13 15:18:54 -05:00
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-msvc --host=x86_64-pc-windows-msvc --target=x86_64-pc-windows-msvc --enable-full-tools --enable-profiler"
Port PGO/LTO/BOLT optimized build pipeline to Rust
2023-06-03 02:41:44 -05:00
SCRIPT: python x.py build --set rust.debug=true opt-dist && PGO_HOST=x86_64-pc-windows-msvc ./build/x86_64-pc-windows-msvc/stage0-tools-bin/opt-dist python x.py dist bootstrap --include-default-paths
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
DIST_REQUIRE_ALL_TOOLS: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-i686-msvc
env:
Make sure we build target-only things (e.g., docs) for host platforms too
2020-09-18 10:56:41 -05:00
RUST_CONFIGURE_ARGS: "--build=i686-pc-windows-msvc --host=i686-pc-windows-msvc --target=i686-pc-windows-msvc,i586-pc-windows-msvc --enable-full-tools --enable-profiler"
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: python x.py dist bootstrap --include-default-paths
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
DIST_REQUIRE_ALL_TOOLS: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
Adds a GitHub Actions CI build for aarch64-pc-windows-msvc via cross-compilation on an x86_64 host. This promotes aarch64-pc-windows-msvc from a Tier 2 Compilation Target (std) to a Tier 2 Development Platform (std+rustc+cargo+tools). Fixes #72881
2020-08-25 12:30:12 -05:00
- name: dist-aarch64-msvc
env:
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-msvc --host=aarch64-pc-windows-msvc --enable-full-tools --enable-profiler"
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: python x.py dist bootstrap --include-default-paths
Sunset RLS
2022-08-20 23:19:43 -05:00
DIST_REQUIRE_ALL_TOOLS: 1
Work around CI issue with windows sdk 10.0.20348.0.
2021-09-10 06:46:15 -05:00
WINDOWS_SDK_20348_HACK: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-i686-mingw
env:
Upgrade mingw-w64 on CI
2022-08-05 14:08:53 -05:00
RUST_CONFIGURE_ARGS: "--build=i686-pc-windows-gnu --enable-full-tools --enable-profiler"
Enable downloading prebuilt LLVM in test builders See comment added for details on the test builder restriction. This is primarily intended for macOS CI, but is likely to be a slight win on other builders too.
2022-07-31 16:45:15 -05:00
NO_DOWNLOAD_CI_LLVM: 1
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: python x.py dist bootstrap --include-default-paths
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
CUSTOM_MINGW: 1
DIST_REQUIRE_ALL_TOOLS: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-x86_64-mingw
env:
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: python x.py dist bootstrap --include-default-paths
Upgrade mingw-w64 on CI
2022-08-05 14:08:53 -05:00
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-gnu --enable-full-tools --enable-profiler"
Enable downloading prebuilt LLVM in test builders See comment added for details on the test builder restriction. This is primarily intended for macOS CI, but is likely to be a slight win on other builders too.
2022-07-31 16:45:15 -05:00
NO_DOWNLOAD_CI_LLVM: 1
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
CUSTOM_MINGW: 1
DIST_REQUIRE_ALL_TOOLS: 1
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: dist-x86_64-msvc-alt
env:
RUST_CONFIGURE_ARGS: "--build=x86_64-pc-windows-msvc --enable-extended --enable-profiler"
Distribute bootstrap in CI artifacts - Add a new `bootstrap` component Originally, we planned to combine this with the `rust-dev` component. However, I realized that would force LLVM to be redownloaded whenever bootstrap is modified. LLVM is a much larger download, so split this to get better caching. - Build bootstrap for all tier 1 and 2 targets
2022-09-14 18:17:05 -05:00
SCRIPT: python x.py dist bootstrap --include-default-paths
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: windows-2019-8core-32gb
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
timeout-minutes: 600
runs-on: "${{ matrix.os }}"
ci: allow gating gha on everything but macOS In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called auto-fallible), allowing us to gate on the auto job without failing due to macOS spurious failures.
2020-06-15 08:12:43 -05:00
steps:
- name: disable git crlf conversion
run: git config --global core.autocrlf false
- name: checkout the source code
update: actions/checkout@v2 to actions/checkout@v3 update: actions/checkout@v2 to actions/checkout@v3 for all yaml files Revert "update: actions/checkout@v2 to actions/checkout@v3 for all yaml files" This reverts commit 7445e582b900f0f56f5f2bd9036aacab97ef28e9. change GitHub Actions version v2 to v3 change GitHub Actions
2022-04-14 00:37:41 -05:00
uses: actions/checkout@v3
ci: allow gating gha on everything but macOS In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called auto-fallible), allowing us to gate on the auto job without failing due to macOS spurious failures.
2020-06-15 08:12:43 -05:00
with:
fetch-depth: 2
ci: allow RLA to pick the right PR number
2020-07-20 10:11:30 -05:00
- name: configure the PR in which the error message will be posted
run: "echo \"[CI_PR_NUMBER=$num]\""
env:
num: "${{ github.event.number }}"
fix env var name
2021-02-25 20:41:25 -06:00
if: "success() && !env.SKIP_JOB && github.event_name == 'pull_request'"
ci: allow gating gha on everything but macOS In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called auto-fallible), allowing us to gate on the auto job without failing due to macOS spurious failures.
2020-06-15 08:12:43 -05:00
- name: add extra environment variables
run: src/ci/scripts/setup-environment.sh
env:
EXTRA_VARIABLES: "${{ toJson(matrix.env) }}"
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: decide whether to skip this job
run: src/ci/scripts/should-skip-this.sh
if: success() && !env.SKIP_JOB
ci: error out if someone sends a PR to the wrong branch
2021-05-06 11:47:37 -05:00
- name: ensure the channel matches the target branch
run: src/ci/scripts/verify-channel.sh
if: success() && !env.SKIP_JOB
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: collect CPU statistics
run: src/ci/scripts/collect-cpu-stats.sh
if: success() && !env.SKIP_JOB
- name: show the current environment
run: src/ci/scripts/dump-environment.sh
if: success() && !env.SKIP_JOB
- name: install sccache
run: src/ci/scripts/install-sccache.sh
if: success() && !env.SKIP_JOB
Bring back XCode selection CI script This reverts commit 8514b0097b28f84ee5cfead059a5771c6a693fb0.
2022-11-19 14:18:09 -06:00
- name: select Xcode
run: src/ci/scripts/select-xcode.sh
if: success() && !env.SKIP_JOB
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: install clang
run: src/ci/scripts/install-clang.sh
if: success() && !env.SKIP_JOB
- name: install WIX
run: src/ci/scripts/install-wix.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
Move submodule checkout before msys2 installation. For some reason, `tar` behaves differently in such a way that it does not create symlinks on Windows correctly, resulting in `Cannot create symlink to 'ld.gold': No such file or directory` errors.
2022-03-01 12:16:47 -06:00
- name: checkout submodules
run: src/ci/scripts/checkout-submodules.sh
if: success() && !env.SKIP_JOB
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: install MSYS2
run: src/ci/scripts/install-msys2.sh
if: success() && !env.SKIP_JOB
- name: install MinGW
run: src/ci/scripts/install-mingw.sh
if: success() && !env.SKIP_JOB
- name: install ninja
run: src/ci/scripts/install-ninja.sh
if: success() && !env.SKIP_JOB
- name: enable ipv6 on Docker
run: src/ci/scripts/enable-docker-ipv6.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
- name: ensure line endings are correct
run: src/ci/scripts/verify-line-endings.sh
if: success() && !env.SKIP_JOB
CI: Verify commits in beta & stable are in upstream branches. Closes #74721
2021-07-29 12:00:13 -05:00
- name: ensure backported commits are in upstream branches
run: src/ci/scripts/verify-backported-commits.sh
if: success() && !env.SKIP_JOB
add script to prevent point releases with same number as existing ones
2022-01-20 14:18:04 -06:00
- name: ensure the stable version number is correct
run: src/ci/scripts/verify-stable-version-number.sh
if: success() && !env.SKIP_JOB
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: run the build
run: src/ci/scripts/run-build-from-ci.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.CACHES_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.CACHES_AWS_ACCESS_KEY_ID)] }}"
TOOLSTATE_REPO_ACCESS_TOKEN: "${{ secrets.TOOLSTATE_REPO_ACCESS_TOKEN }}"
if: success() && !env.SKIP_JOB
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
- name: create github artifacts
run: src/ci/scripts/create-doc-artifacts.sh
if: success() && !env.SKIP_JOB
- name: upload artifacts to github
uses: actions/upload-artifact@v3
with:
name: "${{ env.DOC_ARTIFACT_NAME }}"
path: obj/artifacts/doc
if-no-files-found: ignore
retention-days: 5
if: success() && !env.SKIP_JOB
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: upload artifacts to S3
run: src/ci/scripts/upload-artifacts.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.ARTIFACTS_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.ARTIFACTS_AWS_ACCESS_KEY_ID)] }}"
if: "success() && !env.SKIP_JOB && (github.event_name == 'push' || env.DEPLOY == '1' || env.DEPLOY_ALT == '1')"
try:
Improve job names in Github Actions preview Before: `CI / PR (mingw-check, false, ubuntu-20.04-16core-64gb) (pull_request)` After: `CI / PR - mingw-check (pull_request)`
2023-04-02 16:48:12 -05:00
name: "try - ${{ matrix.name }}"
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
env:
Do not build components unneeded for perf bot in try builds
2023-06-01 01:29:19 -05:00
DIST_TRY_BUILD: 1
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
CI_JOB_NAME: "${{ matrix.name }}"
Enable Cargo's sparse protocol in CI
2023-01-31 20:13:57 -06:00
CARGO_REGISTRIES_CRATES_IO_PROTOCOL: sparse
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
HEAD_SHA: "${{ github.event.pull_request.head.sha || github.sha }}"
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
SCCACHE_BUCKET: rust-lang-ci-sccache2
DEPLOY_BUCKET: rust-lang-ci2
TOOLSTATE_REPO: "https://github.com/rust-lang-nursery/rust-toolstate"
TOOLSTATE_ISSUES_API_URL: "https://api.github.com/repos/rust-lang/rust/issues"
TOOLSTATE_PUBLISH: 1
CACHES_AWS_ACCESS_KEY_ID: AKIA46X5W6CZI5DHEBFL
ARTIFACTS_AWS_ACCESS_KEY_ID: AKIA46X5W6CZN24CBO55
Set the AWS region.
2023-04-30 15:23:48 -05:00
AWS_REGION: us-west-1
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
CACHE_DOMAIN: ci-caches.rust-lang.org
if: "github.event_name == 'push' && (github.ref == 'refs/heads/try' || github.ref == 'refs/heads/try-perf') && github.repository == 'rust-lang-ci/rust'"
strategy:
matrix:
include:
Move back to linux builder on try builds
2021-10-25 08:38:04 -05:00
- name: dist-x86_64-linux
Move us to the new large runners pool For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-18 19:01:33 -05:00
os: ubuntu-20.04-16core-64gb
Move back to linux builder on try builds
2021-10-25 08:38:04 -05:00
env: {}
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
timeout-minutes: 600
runs-on: "${{ matrix.os }}"
steps:
- name: disable git crlf conversion
run: git config --global core.autocrlf false
- name: checkout the source code
update: actions/checkout@v2 to actions/checkout@v3 update: actions/checkout@v2 to actions/checkout@v3 for all yaml files Revert "update: actions/checkout@v2 to actions/checkout@v3 for all yaml files" This reverts commit 7445e582b900f0f56f5f2bd9036aacab97ef28e9. change GitHub Actions version v2 to v3 change GitHub Actions
2022-04-14 00:37:41 -05:00
uses: actions/checkout@v3
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
with:
fetch-depth: 2
- name: configure the PR in which the error message will be posted
run: "echo \"[CI_PR_NUMBER=$num]\""
env:
num: "${{ github.event.number }}"
fix env var name
2021-02-25 20:41:25 -06:00
if: "success() && !env.SKIP_JOB && github.event_name == 'pull_request'"
Move the try builder below the auto builders This allows us to make use of a YAML anchor when specifying the try builder config.
2020-09-26 08:39:53 -05:00
- name: add extra environment variables
run: src/ci/scripts/setup-environment.sh
env:
EXTRA_VARIABLES: "${{ toJson(matrix.env) }}"
if: success() && !env.SKIP_JOB
- name: decide whether to skip this job
run: src/ci/scripts/should-skip-this.sh
if: success() && !env.SKIP_JOB
ci: error out if someone sends a PR to the wrong branch
2021-05-06 11:47:37 -05:00
- name: ensure the channel matches the target branch
run: src/ci/scripts/verify-channel.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: collect CPU statistics
run: src/ci/scripts/collect-cpu-stats.sh
if: success() && !env.SKIP_JOB
- name: show the current environment
run: src/ci/scripts/dump-environment.sh
if: success() && !env.SKIP_JOB
- name: install sccache
run: src/ci/scripts/install-sccache.sh
if: success() && !env.SKIP_JOB
Bring back XCode selection CI script This reverts commit 8514b0097b28f84ee5cfead059a5771c6a693fb0.
2022-11-19 14:18:09 -06:00
- name: select Xcode
run: src/ci/scripts/select-xcode.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: install clang
run: src/ci/scripts/install-clang.sh
if: success() && !env.SKIP_JOB
- name: install WIX
run: src/ci/scripts/install-wix.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
Move submodule checkout before msys2 installation. For some reason, `tar` behaves differently in such a way that it does not create symlinks on Windows correctly, resulting in `Cannot create symlink to 'ld.gold': No such file or directory` errors.
2022-03-01 12:16:47 -06:00
- name: checkout submodules
run: src/ci/scripts/checkout-submodules.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: install MSYS2
run: src/ci/scripts/install-msys2.sh
if: success() && !env.SKIP_JOB
- name: install MinGW
run: src/ci/scripts/install-mingw.sh
if: success() && !env.SKIP_JOB
- name: install ninja
run: src/ci/scripts/install-ninja.sh
if: success() && !env.SKIP_JOB
- name: enable ipv6 on Docker
run: src/ci/scripts/enable-docker-ipv6.sh
if: success() && !env.SKIP_JOB
- name: disable git crlf conversion
run: src/ci/scripts/disable-git-crlf-conversion.sh
if: success() && !env.SKIP_JOB
- name: ensure line endings are correct
run: src/ci/scripts/verify-line-endings.sh
if: success() && !env.SKIP_JOB
CI: Verify commits in beta & stable are in upstream branches. Closes #74721
2021-07-29 12:00:13 -05:00
- name: ensure backported commits are in upstream branches
run: src/ci/scripts/verify-backported-commits.sh
if: success() && !env.SKIP_JOB
add script to prevent point releases with same number as existing ones
2022-01-20 14:18:04 -06:00
- name: ensure the stable version number is correct
run: src/ci/scripts/verify-stable-version-number.sh
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: run the build
run: src/ci/scripts/run-build-from-ci.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.CACHES_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.CACHES_AWS_ACCESS_KEY_ID)] }}"
TOOLSTATE_REPO_ACCESS_TOKEN: "${{ secrets.TOOLSTATE_REPO_ACCESS_TOKEN }}"
if: success() && !env.SKIP_JOB
Publish docs as github artifacts during CI This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-07 18:20:39 -05:00
- name: create github artifacts
run: src/ci/scripts/create-doc-artifacts.sh
if: success() && !env.SKIP_JOB
- name: upload artifacts to github
uses: actions/upload-artifact@v3
with:
name: "${{ env.DOC_ARTIFACT_NAME }}"
path: obj/artifacts/doc
if-no-files-found: ignore
retention-days: 5
if: success() && !env.SKIP_JOB
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
- name: upload artifacts to S3
run: src/ci/scripts/upload-artifacts.sh
env:
AWS_ACCESS_KEY_ID: "${{ env.ARTIFACTS_AWS_ACCESS_KEY_ID }}"
AWS_SECRET_ACCESS_KEY: "${{ secrets[format('AWS_SECRET_ACCESS_KEY_{0}', env.ARTIFACTS_AWS_ACCESS_KEY_ID)] }}"
if: "success() && !env.SKIP_JOB && (github.event_name == 'push' || env.DEPLOY == '1' || env.DEPLOY_ALT == '1')"
master:
name: master
runs-on: ubuntu-latest
env:
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
SCCACHE_BUCKET: rust-lang-ci-sccache2
DEPLOY_BUCKET: rust-lang-ci2
TOOLSTATE_REPO: "https://github.com/rust-lang-nursery/rust-toolstate"
TOOLSTATE_ISSUES_API_URL: "https://api.github.com/repos/rust-lang/rust/issues"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
TOOLSTATE_PUBLISH: 1
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
CACHES_AWS_ACCESS_KEY_ID: AKIA46X5W6CZI5DHEBFL
ARTIFACTS_AWS_ACCESS_KEY_ID: AKIA46X5W6CZN24CBO55
Set the AWS region.
2023-04-30 15:23:48 -05:00
AWS_REGION: us-west-1
ci: upload non-macOS from GHA instead of Azure Pipelines
2020-07-20 10:43:48 -05:00
CACHE_DOMAIN: ci-caches.rust-lang.org
ci: run gha workflows for try, auto and master on the fork
2020-03-20 10:46:45 -05:00
if: "github.event_name == 'push' && github.ref == 'refs/heads/master' && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
steps:
- name: checkout the source code
update: actions/checkout@v2 to actions/checkout@v3 update: actions/checkout@v2 to actions/checkout@v3 for all yaml files Revert "update: actions/checkout@v2 to actions/checkout@v3 for all yaml files" This reverts commit 7445e582b900f0f56f5f2bd9036aacab97ef28e9. change GitHub Actions version v2 to v3 change GitHub Actions
2022-04-14 00:37:41 -05:00
uses: actions/checkout@v3
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
with:
fetch-depth: 2
- name: publish toolstate
run: src/ci/publish_toolstate.sh
Set shell for github actions CI
2020-07-16 12:47:37 -05:00
shell: bash
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
env:
TOOLSTATE_REPO_ACCESS_TOKEN: "${{ secrets.TOOLSTATE_REPO_ACCESS_TOKEN }}"
if: success() && !env.SKIP_JOB
try-success:
needs:
- try
Enable perf try builder This adds a dedicated branch for perf to use for CI, intended to allow perf to enqueue builds without needing to use bors. bors is great, but bors requires an open PR to work, and we want to invoke perf on closed PRs sometimes (in particular, rollups).
2020-07-21 13:53:39 -05:00
if: "success() && github.event_name == 'push' && (github.ref == 'refs/heads/try' || github.ref == 'refs/heads/try-perf') && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
steps:
- name: mark the job as a success
run: exit 0
ci: use bash when executing the "bors build finished" jobs We don't clone the repository in those builders, so the default shell (src/ci/exec-with-shell.py) is not present there.
2020-04-29 09:32:06 -05:00
shell: bash
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
name: bors build finished
runs-on: ubuntu-latest
try-failure:
needs:
- try
Enable perf try builder This adds a dedicated branch for perf to use for CI, intended to allow perf to enqueue builds without needing to use bors. bors is great, but bors requires an open PR to work, and we want to invoke perf on closed PRs sometimes (in particular, rollups).
2020-07-21 13:53:39 -05:00
if: "!success() && github.event_name == 'push' && (github.ref == 'refs/heads/try' || github.ref == 'refs/heads/try-perf') && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
steps:
- name: mark the job as a failure
run: exit 1
ci: use bash when executing the "bors build finished" jobs We don't clone the repository in those builders, so the default shell (src/ci/exec-with-shell.py) is not present there.
2020-04-29 09:32:06 -05:00
shell: bash
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
name: bors build finished
runs-on: ubuntu-latest
auto-success:
needs:
- auto
ci: run the "bors build finished" jobs only during try and auto runs
2020-03-20 12:28:47 -05:00
if: "success() && github.event_name == 'push' && github.ref == 'refs/heads/auto' && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
steps:
- name: mark the job as a success
run: exit 0
ci: use bash when executing the "bors build finished" jobs We don't clone the repository in those builders, so the default shell (src/ci/exec-with-shell.py) is not present there.
2020-04-29 09:32:06 -05:00
shell: bash
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
name: bors build finished
runs-on: ubuntu-latest
auto-failure:
needs:
- auto
ci: run the "bors build finished" jobs only during try and auto runs
2020-03-20 12:28:47 -05:00
if: "!success() && github.event_name == 'push' && github.ref == 'refs/heads/auto' && github.repository == 'rust-lang-ci/rust'"
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
steps:
- name: mark the job as a failure
run: exit 1
ci: use bash when executing the "bors build finished" jobs We don't clone the repository in those builders, so the default shell (src/ci/exec-with-shell.py) is not present there.
2020-04-29 09:32:06 -05:00
shell: bash
ci: add github actions configuration
2019-11-26 05:06:30 -06:00
name: bors build finished
runs-on: ubuntu-latest
Reference in New Issue Copy Permalink