summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* Bump chutneyJim Newsome2026-01-211-2/+2
| | | | Bump chutney, and migrate to CLI changes introduced in chutney!101
* Bump blackJim Newsome2026-01-211-2/+2
|
* Rename check-api-surface CI job and associated scriptIan Jackson2026-01-201-2/+2
| | | | | | | Change the script name to use hyphens, not underscores. Make the script name and the CI job name the same, except the script has -arti at the end in case we add more similar checks.
* CI: Prevent new scripts with snake_case namesIan Jackson2026-01-201-0/+3
|
* CI: Rename cbindgen job to more closely follow script invocationIan Jackson2026-01-201-1/+1
|
* Rename maint/list_crates to kebab-caseIan Jackson2026-01-201-1/+1
| | | | | | | | | | Swap the symlink direction: now we have list_crates.py (the python module) with a symlink list-crates pointing to it. This allows the module to be imported but the command to be kebab case. The checking tooling doesn't understand this special arrangement. Lots of references to update!
* Rename CI functions file to kebab-caseIan Jackson2026-01-201-1/+1
|
* maint: Rename reproducible build scripts to kebab caseIan Jackson2026-01-201-2/+2
| | | | We had both maint/docker-... and maint/docker_...
* maint: Rename miscellaneous scripts to kebab caseIan Jackson2026-01-201-3/+3
|
* CI: Rename cargo-crate-owners job to match scriptIan Jackson2026-01-201-1/+1
|
* Rename remaining maint/check_ to maint/check-Ian Jackson2026-01-201-6/+6
|
* CI: Rename script and job to check-blocking-todosIan Jackson2026-01-201-2/+2
|
* Rename maint/check_tree to maint/check-cargo-treeIan Jackson2026-01-201-1/+1
|
* Rename maint/check_wildcard to check-wildcard-depsIan Jackson2026-01-201-1/+1
| | | | | Use kebab case, and also add the word deps. Otherwise it might refer to files or something.
* Rename cargo_audit and cargo_sort scripts to kebab-caseIan Jackson2026-01-201-2/+2
|
* maint: Rename script and job to cargo-check-targetsIan Jackson2026-01-201-2/+2
| | | | | | The job was called `check-targets` and the script was called `cargo_check_target`. Make them match. Use kebab case, and the plural (it checks multiple targets).
* CI: Add missing cache setting to jobs using via-cargo-install-in-ciIan Jackson2026-01-201-0/+6
| | | | As per the docs for that script.
* Run check_arti_opacity from gitlab CI.Nick Mathewson2026-01-131-0/+8
|
* ci: always run pages jobJérôme Charaoui2025-12-141-0/+1
| | | | | it doesn't depend on anything else in the pipeline, so avoid skipping it when other jobs fail
* Merge branch 'main' into 'main'Alexander Hansen Færøy2025-12-111-4/+37
|\ | | | | | | | | | | | | build website for and deploy to static component Closes tpo/tpa/team#42288 See merge request tpo/core/arti!3547
| * build website for and deploy to static componentJérôme Charaoui2025-12-101-4/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this uses the static-shim-deploy template to deploy the arti website to arti.torproject.org, and tweaks the docusaurus baseUrl accordingly it requires a STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY CI variable which is set up in project settings and contains the private key which allows deployment of assets to static component web hosts it also deploys a "_redirects" file to gitlab pages to ensure that the old URLs are redirected as previously, the website build and deployment jobs are only run in (nightly) scheduled pipelines
* | ci: Keep doc artifactsClara Engler2025-12-111-0/+13
|/ | | | | | | | | | | | Because Rust 1.91.0 makes it economically unfeasiable to run `cargo doc` oneselves, it might wise to keep it as an artifact in `rust-dev-recent` and `rust-nightly`, which generate the docs anyways, so we can keep us away from having to run the expensive command when reviewing (larger) changes to documentation. For now, these artifacts will expire within a week. Maybe this should get discussed, because on my local machine, they are over 2GB large?
* Merge branch 'msrv-ci-check' into 'main'Nick Mathewson2025-11-041-0/+2
|\ | | | | | | | | ci-check-msrv: Add check for MSRV See merge request tpo/core/arti!3405
| * ci-check-msrv: CI check for MSRV declaration in cratesnield2025-10-291-0/+2
| | | | | | | | Checks if each crate has rust-version property in Cargo.toml.
* | CI: bump shadow commitJim Newsome2025-11-031-2/+2
| |
* | ci: image downgrade and comment fix for 'cargo-miri' jobSteven Engler2025-10-311-6/+6
| | | | | | | | | | This downgrades the container image for the 'cargo-miri' job, and updates some adjacent comments.
* | ci: upgrade container versionsSteven Engler2025-10-311-8/+8
|/
* ci: Add needs to almost all jobs.Wesley Aptekar-Cassels2025-10-271-3/+30
| | | | | | | | | | This also updates some needs statements that existed to order jobs that did not actually have a dependency on each other. The idea here is to run everything with as much parallelism as possible, and if that parallelism causes problems, we should ideally solve it by adding more runner capacity, or taking a closer look at what the actual problem is.
* ci: Enable opentelemetry feature in arti-extra build.Wesley Aptekar-Cassels2025-10-231-1/+1
| | | | | I am interested in enabling opentelemetry in chutney tests to enable easier debugging of failures that pop up in CI.
* Merge branch 'msrv-1-86-0' into 'main'David Goulet2025-10-211-1/+1
|\ | | | | | | | | Bump MSRV from 1.85.1 to 1.86 See merge request tpo/core/arti!3382
| * Bump MSRV from 1.85.1 to 1.86Clara Engler2025-10-211-1/+1
| |
* | CI: Specify versions for shellcheck and editorconfig-checker.Wesley Aptekar-Cassels2025-10-161-2/+2
|/ | | | Fixes: #2219
* ci: Parallelize minimal-features-testWesley Aptekar-Cassels2025-10-161-1/+7
| | | | | | | 3 seems like a good number to start with, we can tune it later if needed. Fixes: #2207
* CI: remove 2h timeouts from now-smaller jobsJim Newsome2025-10-091-12/+0
| | | | | Hopefully these are now sufficiently small to fit into the default 1h timeout.
* CI rust-dev-latest: add comment noting that it could be split furtherJim Newsome2025-10-091-0/+5
|
* CI rust-recent-dev-test: split out testJim Newsome2025-10-091-5/+22
| | | | | | | | | | | | This job is still expensive and a bottleneck. "cargo test" is the slowest part, and experimentally doesn't seem to generate artifacts used in the other steps nor reuse artifacts genrated in other steps. Splitting it out to its own job exposes more parallelism. "cargo test" is also more prone to flakiness than the other commands, which just build code without running it. Isolating the flakiness is helpful when we need to retry. (Though of course ultimately we want to eliminate such flakinesss)
* CI rust-recent-dev-test: inline rust-dev-test-script yaml anchorJim Newsome2025-10-091-14/+5
|
* CI: drop rust-latest-integrationJim Newsome2025-10-091-37/+19
| | | | | | | There's probably not much benefit to building these on rust-latest in addition to rust-recent; incompatibilities with rust-latest should be found in rust-latest-dev-test. Let's save the template complexity and CI cost.
* CI: split rust-recent script and jobsJim Newsome2025-10-091-8/+41
| | | | | | | | | | | | rust-recent (and rust-latest, for runs on the main branch) is one of our longer jobs, particularly in the 'build' CI stage, making it a bottleneck for starting the 'test' stage. The job does quite a bit of work, some of it with very little overlap due to use of different cargo build profiles. This commit splits the job roughly by build-profile, so that the work done with each build profile can proceed in parallel.
* CI: build arti-bench with --lockedJim Newsome2025-10-091-1/+1
| | | | | This is mostly for consistency with the following "cargo build" invocation to build arti, but is unlikely to make any real difference.
* CI: build arti-bench with quicktest instead of releaseJim Newsome2025-10-091-2/+2
| | | | | | | | | | | Right now building arti-bench take a fair while in the rust-recent and rust-latest jobs. Using the quicktest profile instead of release makes any actual benchmark results less meaningful, but as far as I can tell this build artifact is mostly just to test that it works at all rather than to collect meaningful performance data. e.g. we're currently not controlling at all for runner capacity or load.
* CI: increase timeout to 2h on some jobsJim Newsome2025-10-081-0/+16
| | | | | | | | This is to mitigate https://gitlab.torproject.org/tpo/tpa/team/-/issues/42317 I added the 2h timeout (overriding the default 1h) for all jobs that were cited as examples on that issue, and a couple others that looked likely to be time-consuming.
* CI: dump /proc/loadavg and /proc/pressure/* for debugging purposesJim Newsome2025-10-081-0/+6
|
* Revert restricting heavy cargo jobs to TPA runnersJim Newsome2025-10-081-12/+0
| | | | | * This reverts commit 8da606966e5213cada270fb64f896f69bab041dd. * This reverts commit a3ac2080956b9295000bd7011c34111a6d5ce5a7.
* CI: limit cargo parallelism based on memory and ncpuJim Newsome2025-10-081-0/+4
| | | | See https://gitlab.torproject.org/tpo/tpa/team/-/issues/42283
* Merge branch 'ci-remove-check-stage' into 'main'wesleyac2025-10-071-5/+4
|\ | | | | | | | | ci: Move "check" jobs into "build" stage. See merge request tpo/core/arti!3318
| * ci: Move "check" jobs into "build" stage.Wesley Aptekar-Cassels2025-10-021-5/+4
| | | | | | | | | | | | | | | | | | | | | | This moves everything that was in the "check" stage into the "build" stage, so that beginning to build the artifacts isn't blocked by running the checks. This should result in CI taking less time overall. There is some concern that making CI more efficient by increasing parallelism could increase load on runners and cause more problems than it solves, so that's something we should look out for in evaluating this change.
* | ci: build fuzz testsSteven Engler2025-10-061-0/+16
| |
* | Merge branch 'ci-move-maint-check-changelog' into 'main'wesleyac2025-10-061-6/+1
|\ \ | | | | | | | | | | | | ci: Move maint-check-changelog into maint-checks. See merge request tpo/core/arti!3316
| * | ci: Move maint-check-changelog into maint-checks.Wesley Aptekar-Cassels2025-10-021-6/+1
| |/ | | | | | | | | | | | | | | | | | | I hope that this will reduce the load on our CI and speed up these checks. This should also cause this check to run earlier in the process, which is nice for finding issues earlier. It's unclear to me if there was a specific reason this was a separate job. As far as I can tell from the commit message and discussion in !2126, there does not seem to be a specific reason.