summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* arti-extra build: enable onion-service-serviceJim Newsome2023-12-131-1/+1
|
* arti-extra build: no-op reformatJim Newsome2023-12-131-1/+5
|
* Enable ntor_v3 in the arti-extra buildJim Newsome2023-12-071-1/+1
| | | | This tests ntor_v3 in the shadow integration test.
* Merge branch 'msrv-bump-1.70' into 'main'Ian Jackson2023-11-301-3/+1
|\ | | | | | | | | Increase our MSRV to 1.70 See merge request tpo/core/arti!1773
| * CI: change minimal-versions to 1.70.Nick Mathewson2023-11-281-3/+1
| |
* | Fix extra features getting enabled in the arti-extra test binaryJim Newsome2023-11-281-1/+5
|/ | | | | | | We were missing `-p arti` in the build command. As a result we were getting the union of all features requested by anything in the workspace, including an example enabling the `experimental` feature which enables a bunch of other things.
* use ipv6 runner instead of tpa for coveragetrinity-1686a2023-11-221-1/+1
|
* add tpa tag to coverage-aggregatedtrinity-1686a2023-11-161-0/+2
| | | | otherwis it fails when it gets scheduled on a non-ipv6 ready runner
* update rustc for reproducible buildstrinity-1686a2023-11-161-1/+1
|
* remove artifact generation from rust-latest-test-all-featurestrinity-1686a2023-10-131-5/+0
|
* move usage of ./maint/preserve out of after_scripttrinity-1686a2023-10-131-3/+3
|
* CI: Remove amd64 tagsIan Jackson2023-09-181-18/+0
| | | | | | | | | | | | | | | We have a new runner, and apparently to use it better we want to remove these tags. TBH this seems rather unprincipled. In theory, shouldn't we tag with `amd64` all the jobs that we definitely want to run on that arch, and the others can run on whatever is the default? Then in the glorious distant RISCV future everything will run on riscv64 by default? But maybe we wouldn't want to switch that as part of the infrastructure anyway? Anyway, for discussion see https://gitlab.torproject.org/tpo/tpa/team/-/issues/41295#note_2943129
* CI: Ensure libssl3 is installed in shadow and chutney testsJim Newsome2023-09-051-4/+4
|
* CI: Ensure libsqlite3 is installed in shadow and chutney testsJim Newsome2023-09-051-0/+5
|
* Update CI to use Debian bookworm instead of bullseyeJim Newsome2023-08-291-18/+18
|
* shadow test: use libigraph from bullseyeJim Newsome2023-08-291-2/+20
| | | | Workaround for https://github.com/shadow/tgen/issues/44
* CI: Replace all uses of `debian:stable-slim` with `bookworm`Ian Jackson2023-08-251-4/+4
| | | | | | | | Thesee jobs are ones which don't interact with our Rust executables. Since `debian:stable-slim` has already been updated I believe, I think this actually makes no difference right now. But it will prevent us unexpectedly picking up Debian updates.
* CI: Replace all uses of `rust:latest` image with `rust:bullseye`Ian Jackson2023-08-251-13/+13
| | | | | `rust:latest` updates to a new Debian willy-nilly, which broke our CI due to it being an uncontrolled dependency.
* CI: cargo install caching: Use cache/ directory, per-imageIan Jackson2023-08-251-5/+4
| | | | | | This avoids us trying to run binaries built on one image, on a different one. I believe that this is supposed to work according to Rust doctrine, but empirically it doesn't.
* CI: Use apt, not pip, to install python packages.Nick Mathewson2023-08-251-5/+2
| | | | | Debian's pip3 now apparently complains when root is running it, which breaks our old coverage CI.
* CI: Remove unneeded install of git in maint-checksIan Jackson2023-08-091-1/+1
| | | | | | | This was added in 9357a8fd6b22 "ci: add shebang to the GitLab CI" as part of !990 to the `maint-checks` job; but the actual additional check was added to the `doc-features` job (by mistake, fixed in !1490); and, that shebang check script doesn't need git anyway.
* ci: move shebang check into proper CI testEmil Engler2023-08-091-1/+1
| | | | | | | Currently, the shebang check CI is not executed, as it would need to fail then. See !1489
* Disable chutney test againIan Jackson2023-08-091-0/+3
|
* Add maint/check_all_lockfilesMicah Elizabeth Scott2023-08-031-0/+1
| | | | | Looks for any checked-in Cargo.lock files, and checks the lockfile quickly by running `cargo tree --locked` there.
* CI: Remove extraneous whitespace.Gabriela Moldovan2023-07-121-1/+1
|
* CI: Remove unnecessary --feature flag.Gabriela Moldovan2023-07-121-1/+1
| | | | | `onion-service-client` is now a default feature, so we don't need to explicitly enable it anymore.
* CI: Add a job for building arti with additional features.Gabriela Moldovan2023-07-111-0/+28
| | | | | | | This is needed for testing `experimental-api` features (such as the keymgr) in shadow and chutney. Prompted by this discussion: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1399#note_2921294
* fix chutney in CItrinity-1686a2023-07-081-2/+3
|
* Merge branch 'shadow-onion' into 'main'Nick Mathewson2023-07-051-1/+1
|\ | | | | | | | | CI: extend shadow test to test an onion service connection See merge request tpo/core/arti!1292
| * CI: enable onion-service-client in rust-latest buildJim Newsome2023-07-031-1/+1
| | | | | | | | | | The shadow test needs this to use this build when testing onion services.
* | try making CI fastertrinity-1686a2023-07-041-2/+4
|/
* CI: run a normal all-features-testIan Jackson2023-06-281-0/+17
| | | | | | | | | I think we do actually do this as part of the coverage job, but that's not really very clear (and getting the report in that job may be annoying). We also do it on nightly as part of the nightly test, but that's an "allow_fail".
* lints: Promote clippy::print_stderr and clippy::print_stdoutIan Jackson2023-06-211-1/+1
| | | | | | | | These are available in our MSRV now, so we don't need to handle specially. We can just add them to the standard lint block. (Lint block in every crate will be updated automatically in the next commit.)
* CI: Upgrade every-crate test to requiredIan Jackson2023-06-141-2/+0
| | | | Since it passes now.
* CI: test every crate with default featuresIan Jackson2023-06-141-0/+9
|
* CI: integration-chutney: Turn into a warningIan Jackson2023-06-131-0/+1
| | | | | | | | This test is known to fail "when the load is high". Recently I had to press the "merge unverified changes" button to merge !1238, after four consecutivew spurious failures. IMO this is intolerable.
* shadow ci: bump tgenJim Newsome2023-05-221-1/+1
|
* shadow ci: bump shadowJim Newsome2023-05-221-1/+1
|
* Bump Rust version in reproducible build scriptsNick Mathewson2023-04-131-1/+1
| | | | Now that we require 1.65, Rust 1.63 is no longer sufficient.
* Run cargo audit last and in its own jobIan Jackson2023-04-121-3/+16
| | | | | Recently we had some minor awkwardness due a new advisory. This may help in future.
* Test with 1.65 in minimal_versions.Nick Mathewson2023-04-111-1/+1
|
* maint/check_todos: Run in CIIan Jackson2023-03-211-0/+9
|
* ci: add shebang to the GitLab CIEmil Engler2023-01-261-1/+2
|
* Maine ./maint/check_doc_feature a warningIan Jackson2023-01-301-0/+10
| | | | | | | | | | This is a fair amount of manual work to keep in sync. I would like to disable this, at least as a mandatory check, for now. Fixes #601 (the request for it to become non-blocking). The underlying issue is #581 and remains open. Co-authored-by: trinity-1686a <[email protected]>
* maint: replace llvm-tools-preview with llvm-toolsEmil Engler2023-01-271-2/+2
| | | | | | | | | | | | This commit replaces all occurrences of `llvm-tools-preview` with `llvm-tools`, because it became a stable feature with Rust 1.60, thereby making the `-preview` prefix obsolete. Beside this, `llvm-tools-preview` is a redirection to the latter one anyway. However, it does not work the other way around. At the moment, it is not possible to execute the `maint/coverage` script on a NixOS system, because the rustup component list only includes `llvm-tools`, but not `llvm-tools-preview`, thereby making this change necessary.
* put ci log span magic strings in a dedicated scripttrinity-1686a2022-12-051-2/+2
|
* update shadow and install tsharktrinity-1686a2022-11-301-1/+5
|
* CI: test that we can compile, and test cfg, with/without bridges/PTsIan Jackson2022-11-291-0/+6
|
* Switch CI back to nightly.Nick Mathewson2022-11-241-3/+7
| | | | | | | | | | | | Now that they have merged https://github.com/rust-lang/rust/pull/104416 , our CI should pass again with the regular nightly image. Rather than remove the pinned image entirely, I'm commenting it out, with a comment explaining how to pin an image the next time we need to do so. Closes #633.
* gitlab-ci: Pin to nightly-2022-11-11Nick Mathewson2022-11-181-1/+3
| | | | This is a workaround for #633.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:48:21 +0000