summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Use rust 1.60 in minimal-versions.Nick Mathewson2022-11-101-1/+1
| | | | Closes #621
* Check more targetstrinity-1686a2022-11-101-0/+10
|
* cleanup target dir on job completiontrinity-1686a2022-10-211-2/+17
|
* Merge branch 'matrix-features' into 'main'Nick Mathewson2022-10-211-0/+8
|\ | | | | | | | | | | | | add checks for many feature combinations Closes #303 See merge request tpo/core/arti!775
| * move test to dedicated jobtrinity-1686a2022-10-171-2/+8
| |
| * add test for many featurestrinity-1686a2022-10-161-0/+2
| | | | | | | | and fix issue compiling tor-rtcompat with on ssl runtime
* | integration-shadow: "shadow-small" tag -> "tpa"Jim Newsome2022-10-191-1/+1
|/ | | The "shadow-small" tag no longer exists, and all "tpa" x86-64 runners can now run Shadow. https://gitlab.torproject.org/tpo/tpa/team/-/issues/40833#note_2835576
* Create a shadow-based integration testJim Newsome2022-10-051-1/+85
| | | | Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/174
* CI: build-repro: Bump image to 1.63Ian Jackson2022-09-061-1/+1
| | | | | | | | | tinystr 0.6.2 (which our Cargo.toml's permit and our Cargo.lock specifies) has an MSRV of 1.60. The symptom with earlier Rust is this from cargo: error: failed to select a version for the requirement `tinystr = "^0.6.0"` (which is, on the face of it, nonsense).
* switch from awk to pythontrinity-1686a2022-08-241-1/+1
|
* add check_doc_features to CItrinity-1686a2022-08-241-1/+2
|
* enable doc_auto_cfg feature on every crate when documenting for docs.rstrinity-1686a2022-08-241-1/+1
|
* maint/add_warning: Scan all files by default, but insist only in someIan Jackson2022-06-241-1/+1
| | | | | | | This will allow us to have add_warning manage test lint blocks. We have to stop printing all the filenames because there are too many. Filenames still come out on error of course.
* ci: Pass --cfg ci_arti_stable to stable clippyIan Jackson2022-06-231-1/+1
| | | | We're going to use this to control lints etc.
* Merge branch 'ring_out_the_old' into 'main'Ian Jackson2022-06-171-0/+1
|\ | | | | | | | | Enforce no-ring-in-arti/full (and make it true) See merge request tpo/core/arti!592
| * Don't install cargo-tree: It's built-in.Nick Mathewson2022-06-161-2/+1
| |
| * Add script and CI to make sure `ring` doesn't show up in arti/fullNick Mathewson2022-06-161-1/+3
| | | | | | | | See arti#493.
* | gitlab-ci: Use lowercase tpa tag.Nick Mathewson2022-06-161-1/+1
|/ | | | Our gitlab admins are standardizing on this variant.
* Merge branch 'clippy' into 'main'Nick Mathewson2022-06-091-0/+1
|\ | | | | | | | | clippy: Allow dbg in tests *again* See merge request tpo/core/arti!575
| * clippy: Allow dbg in tests *again*Ian Jackson2022-06-081-0/+1
| | | | | | | | *sigh*
* | CI: Break out maint/via-cargo-installIan Jackson2022-06-081-7/+2
| |
* | CI: Break out some fastish Rust checks into new "build" stepIan Jackson2022-06-081-7/+15
| |
* | CI: Break out some fast checks using debian imageIan Jackson2022-06-081-3/+8
| |
* | maint/check_toposort: Run in CIIan Jackson2022-06-081-0/+2
|/
* Merge branch 'check-license-fixes' into 'main'Ian Jackson2022-06-021-0/+3
|\ | | | | | | | | | | | | Update check_licenses and add it to CI. Closes #462 See merge request tpo/core/arti!559
| * Add check_licenses to CI.Nick Mathewson2022-05-311-0/+3
| | | | | | | | | | The artifact-caching logic is taken from other examples in the .gitlab-ci.yml.
* | maint/add_warning: Run with --check in CIIan Jackson2022-05-311-0/+1
|/
* Lexically sort Cargo.toml dependenciesOrhun Parmaksız2022-05-281-0/+4
| | | | | | Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <[email protected]>
* Merge branch 'standardise-shell' into 'main'Nick Mathewson2022-05-261-1/+2
|\ | | | | | | | | | | | | Standardise shell Closes #425 See merge request tpo/core/arti!533
| * make almost all scripts use bash and set euo pipefailtrinity-1686a2022-05-251-1/+2
| |
* | ci: set umask instead of ARTI_FS_DISABLE_PERMISSION_CHECKSAlex Xu (Hello71)2022-05-251-6/+7
|/
* Update Gitlab CI config for Gitlab 14.10eta2022-05-231-1/+3
| | | see https://gitlab.com/gitlab-org/gitlab/-/issues/344533
* Disable fs-mistrust in coverage CI.Nick Mathewson2022-05-101-0/+3
| | | | | The CI runners like to run as root with umask 000, which our code rightly freaks out about.
* Merge branch 'use-fs-mistrust'Nick Mathewson2022-05-091-0/+3
|\
| * gitlab-ci: Disable fs mistrust in integration testNick Mathewson2022-05-051-0/+3
| | | | | | | | | | | | The environment where the test runner does its thing seems to want to run as root with umask 000, which naturally makes the fs permissions checks freak out.
* | only deploy pages on maintrinity-1686a2022-05-051-1/+1
| |
* | add schedulable job to generate aggregated coveragetrinity-1686a2022-05-051-6/+45
|/
* CI: Check that the lockfile is up to date.Ian Jackson2022-05-041-1/+1
| | | | | | | | | | For at least one job, run the first cargo run with --locked. This will fail if the lockfile needs updating. I have verified that this correctly detects this situation: https://gitlab.torproject.org/Diziet/arti/-/pipelines/37692 failed. Now I have rebased this branch onto main to get the fix to Cargo.lock.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:47:50 +0000