summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* CI: bump shadow commitJim Newsome2026-07-271-2/+2
| | | | Primarily to get <https://github.com/shadow/shadow/pull/3767>
* integration-e2e-shadow: use shadowtools.config to typecheck generated shadow ↵Jim Newsome2026-07-271-3/+11
| | | | | | | | | config * build shadowtools python package in `build-shadow` job * install the shadowtools python package in python3-checks, so that usage can be checked with mypy. * integration-e2e-shadow: generate typed shadow config
* integration-e2e-shadow: change default data-dir to TOPLEVEL/chutney-netJim Newsome2026-07-231-2/+2
|
* integration-e2e-shadow: move artifacts into nodes dirJim Newsome2026-07-231-5/+0
| | | | | This keeps everything together and avoids clobbering previous artifacts, since chutney already creates a unique nodes dir in every run.
* ci: replace image:docker:platform key with tagJérôme Charaoui2026-07-201-8/+2
| | | | | | | | | | | | | | | | | the recent update to gitlab-runner 19.2.0 has introduced incompatibilities which make using this key with our podman backend produce runner failures, see tpo/tpa/team#42731 this key was originally added as an attempt to coerce the container runtime to always pull an amd64 image after it was observed that sometimes, an i386 image was pulled instead however, since switching registries from dockerhub to registry.tpo, this can almost certainly never happen again since the base-images project doesn't even build i386 containers instead, just tag all jobs by default with the amd64 to ensure only such runners can ever pick up those jobs
* CI: bump chutney versionJim Newsome2026-07-011-2/+2
| | | | Primarily to get chutney!152, which should mitigate arti#2576
* CI: Condense "image" declarations for nightly.Nick Mathewson2026-07-011-7/+8
|
* CI: Pin nightly to 2026-06-28 to resolve internal compiler errorNick Mathewson2026-07-011-4/+9
| | | | See #2616
* CI: In check-api-surface, do not specify +nightlyNick Mathewson2026-07-011-1/+2
| | | | | | (The script will add +nightly unless we override $CARGO. But using +nightly here will prevent us from pinning the rust nightly version in our CI.)
* CI; Mark check-api-surface as may-failNick Mathewson2026-06-301-0/+2
| | | | See #2616.
* Revert "ci: require 'tpa' tag for runners"Steven Engler2026-06-251-4/+0
| | | | This reverts commit 75c0ee2f90710b6d599076debcb6ffad49599823.
* ci: require 'tpa' tag for runnersSteven Engler2026-06-241-0/+4
| | | | | | | | | | This is to try to work around the following, since the OSUOSL runners are broken. https://gitlab.torproject.org/tpo/tpa/team/-/work_items/42705 We should revert this once they are working again. I'll open a ticket to remember do this.
* Merge branch 'msrv-1.91' into 'main'gabi-2502026-06-181-1/+1
|\ | | | | | | | | Bump MSRV to 1.91 See merge request tpo/core/arti!4105
| * Bump MSRV to 1.91Clara Engler2026-06-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit bumps the MSRV to 1.91 which was released on 2025-10-30. The Cargo.toml files were updated as follows: ```sh git ls-files | \ grep ".*Cargo\.toml$" | \ xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g' ``` The following files were updated manually: ``` modified: .gitlab-ci.yml modified: README.md modified: flake.nix modified: maint/docker-android/Dockerfile ```
* | Bump chutney to get Stable flag fixJim Newsome2026-06-151-2/+2
|/ | | | | | | | | | This is primarily to get chutney!149. This should fix arti#2463, but I haven't been able to repro locally to verify. I suspect it'll mitigate some of the other difficult-to-repro cases of arti#2209 as well.
* CI: Update RECENT_RUST_IMAGE to 1.96Gabriela Moldovan2026-06-081-1/+1
|
* CI: Bump build-repro docker images to rust 1.96Gabriela Moldovan2026-06-081-1/+1
| | | | Part of #2559
* CI: bump shadow commitGabriela Moldovan2026-06-031-2/+2
| | | | | | Needed so we can upgrade to the latest `filetime`. See #2562
* CI: turn on RUST_BACKTRACE for all jobsIan Jackson2026-05-181-0/+2
| | | | | | | I just had a situation where the backtrace might have been helpful, arti#2538, https://gitlab.torproject.org/Diziet/arti/-/jobs/1539809. I was surprised to find we don't seem to turn this on and never have!
* CI: Disable cargo-fuzz test for nowIan Jackson2026-05-131-0/+3
| | | | | This test is known to fail, and we have had a ticket for it for a week now. It should be re-enabled if and when it works again.
* Update to Rust 1.95.0 for build-repro CI job.Wesley Aptekar-Cassels2026-05-071-1/+1
|
* ci: re-enable 'flowctl-cc' and 'counter-galois-onion' in arti-extraSteven Engler2026-04-141-5/+3
|
* CI: bump chutney versionJim Newsome2026-04-081-2/+2
| | | | | | Mostly to get logging improvements chutney!124. Also work around a potential race condition, though I don't think we've observed it in CI chutney!125
* CI: bump chutneyJim Newsome2026-04-021-2/+2
| | | | | Primarily to get recent improvements to bootstrap checking and reporting.
* CI: Update Rust to 1.94.1Ian Jackson2026-04-021-2/+2
|
* CI: Give path to script to updateIan Jackson2026-04-021-1/+1
|
* CI: Update Alpine for Rust to 3.22Ian Jackson2026-03-311-1/+1
|
* CI: Update Rust to 1.94Ian Jackson2026-03-311-2/+2
|
* arti-extra: don't include flowctl-cc or counter-galois-onionJim Newsome2026-03-181-8/+24
| | | | | | | Including these would introduce flakiness, until arti#2400 is resolved. This also adds a general mechanism for omitting specific features in the arti-extra build.
* arti-extra build: enable everything in full and experimentalJim Newsome2026-03-181-9/+5
| | | | | | | | | | | Previously we enabled features piecemeal to avoid enabling `rpc`, which resulted in breakage when running under shadow. Experimentally, this appears to no longer be the case. Enabling everything in `full` and `experimental` gives us at least a little bit of testing of those features (that they don't break the build or other usage), even if we don't specifically exercise them (yet) in the CI tests.
* chutney test: include arti-extra binJim Newsome2026-03-111-1/+1
| | | | | Test the arti-extra bin, which includes most of `full` and `experimental` features, too.
* python lints: install chutneyJim Newsome2026-03-041-3/+4
| | | | | mypy needs it to correctly type-check the chutney test scripts, which now import chutney as a module
* chutney test: bump CHUTNEY commit and update to test all endpointsJim Newsome2026-03-041-2/+2
| | | | | | | chutney replaced Node.socksport (a single optional port) with Node.socksport_endpoints (a sequence of bound addresses and ports). Update for compatibility, and test all of the exposed endpoints where relevant.
* chutney test: drop jq dependencyJim Newsome2026-03-041-2/+1
|
* Add compare_to check for cargo-audit changes rules check.Alexander Hansen Færøy2026-02-191-1/+3
| | | | | | See: arti#2367 See: arti!3703 See: arti!3690
* Allow cargo-audit CI job to fail for MR's with no changes to **/Cargo.lock.Alexander Hansen Færøy2026-02-181-0/+22
| | | | | | | | | | | | | | | | | | | This patch changes the behaviour of our `cargo-audit` CI job: - All non-merge requests (pushes, manual jobs, scheduled jobs, tags, etc.) will continue to run with allow_failure set to false. - When a push is made, where there are changes to `**/Cargo.lock`, we continue to NOT allow failures. - When a push is made, where there are NO changes to `**/Cargo.lock`, we now allow failures. Specify workflows for Arti in our GitLab CI configuration: - We currently run our jobs on pushes, and upon tags. This was discussed in the Network Team meeting on 2026-02-10.
* Bump MSRV from 1.86 to 1.89Gabriela Moldovan2026-02-161-1/+1
| | | | | | | As agreed at our last team meeting. See https://gitlab.torproject.org/tpo/core/arti/#minimum-supported-rust-version
* ci: Check crates configure features published to docs.rsNiel Duysters2026-02-091-0/+1
| | | | | | All (publishable) crates should explicitly configure what features to (not) document in docs.rs. This to avoid our documentation containing references to public API specifications which yield "given resource not found" due to them being behind a feature flag not being published to docs.rs by default.
* ci: Update editorconfig-checker version.Wesley Aptekar-Cassels2026-02-021-1/+1
|
* 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
|
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:46:06 +0000