summary refs log tree commit diff
path: root/src/ci/scripts
AgeCommit message (Collapse)AuthorLines
2025-02-17Revert "add new CI step: "setup upstream remote""Pietro Albini-24/+0
This reverts commit 4454fa998c9da1f1eee1602c8e8cd2732505c104. (cherry picked from commit 395fb701e74f58e6c77e2cbdc1967478924e819f)
2024-12-31Reformat Python fileJakub Beránek-2/+12
2024-12-30chore: fix typosHoru-1/+1
2024-12-16[CI] Use a lockfile for installing the `datadog` packageJakub Beránek-8/+6
Without a lockfile, it could fail to compile when the dependencies have changed.
2024-12-04Reformat Python code with `ruff`Jakub Beránek-12/+9
2024-10-12add new CI step: "setup upstream remote"onur-ozkan-0/+24
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-02Auto merge of #125771 - Kobzol:ci-datadog-metrics, r=jdnobors-0/+81
[CI] Upload average CPU utilization of CI jobs to DataDog This PR adds a new CI step that uploads the average CPU utilization of the current GH job to Datadog. I want to add more metrics in follow-up PRs. r? `@jdno` try-job: dist-i686-msvc try-job: aarch64-apple try-job: x86_64-gnu-llvm-18
2024-09-27Partially revert "ci: Use mv instead of cp in upload step"Jubilee Young-3/+3
This partially reverts commit fe7c97c2e732de8dfc93ef21ee84ccfbc04c7d0c. I kept a mv, not a cp, for the one that shuffles major artifacts around, because the size of those artifacts are big enough to matter, sometimes. I don't think the diagnostic info will be that heavy, by comparison.
2024-09-27Revert "ci: Try to remove unused Xcode dirs"Jubilee Young-17/+0
This reverts commit 06f49f6d5326440192b8d31d69fa490dbfe01cfe.
2024-09-27Upload average CPU consumption of CI jobs to DataDogJakub Beránek-1/+82
2024-09-01Upgrade CI's mingw-w64 toolchainMateusz Mikuła-2/+2
2024-08-30ci: Take tail instead of head to avoid broken pipesJubilee Young-3/+1
2024-08-30ci: Avoid legacy backticks in upload-artifacts.shJubilee Young-1/+1
2024-08-30ci: Use mv instead of cp in upload stepJubilee Young-4/+4
2024-08-30ci: Try to remove unused Xcode dirsJubilee Young-0/+17
2024-07-07use "bootstrap" instead of "rustbuild" in comments and docsonur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-05-28Rollup merge of #125590 - ChrisDenton:mingw-ci-3, r=KobzolMatthias Krüger-42/+5
Add a "Setup Python" action for github-hosted runners and remove unnecessary `CUSTOM_MINGW` environment variable The Setup Python action isn't strictly necessary ([even on Windows](https://github.com/rust-lang/rust/pull/125584)) but it is [recommend by GitHub](https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#specifying-a-python-version). The `CUSTOM_MINGW` environment variable is redundant now as it's always set for mingw and always unset otherwise. try-job: x86_64-mingw try-job: x86_64-mingw try-job: dist-x86_64-msvc try-job: dist-x86_64-mingw
2024-05-27Use grep to implement verify-line-endingsChris Denton-11/+11
2024-05-27Update description of install-mingwChris Denton-2/+1
2024-05-26Cleanup custom mingw in CIChris Denton-40/+4
2024-05-26Do less reinstalling in mingw CIChris Denton-41/+4
2024-05-09Upgrade the version of Clang used in the build, move MSVC builds to Server 2022Daniel Paoliello-5/+11
2024-04-24Remove `should-skip-this.sh`Jakub Beránek-21/+0
2024-04-20Move calculate-job-matrix.py to `ci/github-actions`Jakub Beránek-25/+0
2024-04-15Auto merge of #123451 - Kobzol:arbitrary-try-build, r=pietroalbinibors-0/+25
CI: add a script for dynamically computing CI job matrix It would be great if was easier to run specific CI workflows locally, and also to allow us to spawn a specific CI workflow by bors, to enable running arbitrary try builds. See discussion [here](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/CI.20workflows.20refactoring). This PR is a first step in that direction. - Moves the definition of CI runners and (for now) PR jobs into a separate `jobs.yml` file. - Adds a simple Python script that reads the file, decides which jobs should be active for the current CI workflow, and prints them as JSON to their output. - The PR job then reads this output and generates its job matrix based on it. By moving the job definitions from `ci.yml` into a separate file, we can handle it programmatically, which should make it easier to both do local execution of CI jobs and also to do arbitrary try builds.
2024-04-04Generate CI job matrix for PR jobs in PythonJakub Beránek-0/+25
2024-04-03Output URLs of CI artifacts to GitHub summaryJakub Beránek-0/+14
2024-03-28Update ninja on WindowsNilstrieb-1/+1
Errors started showing up, and I read somewhere that this might be because of old ninja versions. This ninja version is indeed *ancient*. ``` multiple outputs aren't (yet?) supported by depslog; bring this up on the mailing list if it affects you ```
2024-03-17Auto merge of #122321 - majaha:mingw_ci_new, r=Mark-Simulacrumbors-10/+13
`mv` tools off the path instead of `rm -r`-ing them in `install-msys2.sh` This is a follow up patch to https://github.com/rust-lang/rust/pull/121182 r? `@Mark-Simulacrum`
2024-03-11mv instead of rm tools off path for msys2 installMatt Harding-10/+13
2024-03-10Rollup merge of #122125 - majaha:mingw_ci_new, r=Mark-SimulacrumMatthias Krüger-6/+8
Revert back to Git-for-Windows for MinGW CI builds Following discussion in https://github.com/rust-lang/rust/pull/121182 it was decided to revert using MSYS2 Git for mingw builds.
2024-03-07Revert back to Git-for-Windows for MinGW CI buildsMatt Harding-6/+8
In https://github.com/rust-lang/rust/pull/121182 the mingw build was changed to use MSYS2's version of Git. This commit reverts that, as it was considered too slow.
2024-02-25Auto merge of #121182 - majaha:mingw_ci_new, r=Mark-Simulacrumbors-14/+37
Improvements to building and CI for mingw/msys I was getting error messages when trying to follow the build instructions the mingw build for Rust, and managed to track the issue down to an incomparability of Rust's bootstrap program with MSYS2's version of git. Essentially, the problem is that MSYS2's git works in emulated unix-y paths, but bootstrap expects a Windows path. I found a workaround for this by using relative paths instead of absolute paths. Along with that fix, this PR also updates the build instructions for MinGW to be compatible with modern versions of MSYS2, and some changes to CI to make sure that MSYS2's version of git is tested. In particular, I'm suggesting using the [MSYS2 github action](https://github.com/marketplace/actions/setup-msys2) specially made for this purpose, which is much less hacky than the old approach and gives us more control of what packages are installed. I also cleaned up as many alternate versions of key tools as I could find from PATH, to avoid accidental usage, and cleaned up some abuses of the `CUSTOM_MINGW` environment variable. This fixes https://github.com/rust-lang/rust/issues/105696 and fixes https://github.com/rust-lang/rust/issues/117567
2024-02-16Changes to CI related to mingw and MSYSMatt Harding-14/+37
2024-02-10Require that SELECT_XCODE is set.Eric Huss-3/+1
Allowing the Xcode version to "float" based on whatever default GitHub selects creates an unreliable environment. When GitHub changes the default, we can have multiple jobs in the same run using different versions as it rolls out across machines. It can also cause oscillation between runs as different machines are used. It also causes unpredictable timing when the updates happen. This change helps ensure that the version that is used is pinned. The downside is that it requires manually bumping the version, and the risk that if we take too long, older Xcodes will be removed and that will break the build.
2024-01-31CI: Use ninja on apple buildersEric Huss-0/+2
2024-01-10Add debug info for macOS CI actionsEric Huss-0/+16
2023-11-11merge `if-available` and `if-unchanged` for `download-ci-llvm`onur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-11-08Install tidy for aarch64-apple-darwinJake Goulding-0/+24
The GitHub Actions image has this preinstalled for x86_64 but not M1.
2023-10-09Install `awscli` on the aarch64-apple-darwin builderJake Goulding-0/+29
Unlike the other builders, this one doesn't come with it preinstalled.
2023-10-05Enable new bors try branch to run on CIJakub Beránek-1/+1
2023-09-25Fix jq in CIMichael Goulet-1/+1
2023-07-19remove hack, now CI uses (currently latest) SDK 10.0.22621.0klensy-5/+0
See https://github.com/rust-lang-ci/rust/actions/runs/5596259246/jobs/10233070602#step:24:929 C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_io.h
2023-06-12Publish docs as github artifacts during CITrevor Gross-0/+42
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-04-28Remove aws cli install.Eric Huss-38/+0
2023-04-28Update awscliEric Huss-3/+4
2023-03-11Auto merge of #109001 - matthiaskrgr:rollup-a3agnwp, r=matthiaskrgrbors-0/+2
Rollup of 8 pull requests Successful merges: - #105798 (Relax ordering rules for `asm!` operands) - #105962 (Stabilize path_as_mut_os_str) - #106085 (use problem matchers for tidy CI) - #107711 (Stabilize movbe target feature) - #108017 (Add `--no-undefined-version` link flag and fix associated breakage) - #108891 (Remove an extraneous include) - #108902 (no more do while :<) - #108912 (Document tool lints) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2023-03-09record the cpu usage in a gitignored directoryPietro Albini-2/+3
2023-03-06use problem matchers for tidy CIDeadbeef-0/+2
2023-02-05Run the tools builder on all PRsJoshua Nelson-36/+1
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).
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 17:26:55 +0000