summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* docs: Only mv coverage directory if it's available.Alexander Hansen Færøy2025-01-301-1/+1
| | | | This is useful when testing just the publish target.
* docs: Simplify command.Alexander Hansen Færøy2025-01-301-1/+1
|
* docs: Reorder deployment commands for making the old site available.Alexander Hansen Færøy2025-01-301-4/+7
|
* docs: Build Docusaurus website as part of our CI pipeline for scheduled ↵Alexander Hansen Færøy2025-01-301-3/+13
| | | | website builds.
* CI: Update RECENT_RUST_IMAGE to 1.83.Nick Mathewson2025-01-071-1/+1
|
* gitlab-ci: pin some python tool versions.Nick Mathewson2025-01-051-1/+4
|
* CI: allow the python3-checks job to passIan Jackson2025-01-021-0/+1
| | | | | I don't know how to pin the versions as I request in #1788. Tolerate the failure for now.
* .gitlab-ci.yml: pin to cbindgen 0.27.0Nick Mathewson2024-12-111-1/+1
| | | | | | | | This will help us avoid bugs related to using multiple versions in the future. (From time to time, we should upgrade to more recent versions as they become available.)
* Use TPA-maintained debian imageJim Newsome2024-12-041-2/+4
| | | | | | This is primarily to reduce usage of our dockerhub pull quota. See https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/ci#tpa-maintained-images
* chutney CI: use virtualenvs instead of --break-system-packagesJim Newsome2024-11-061-5/+6
| | | | | This doesn't actually matter much when run in CI, but provides a better example for running locally.
* CI: Use pip to install chutney directly from remote repositoryJim Newsome2024-11-061-19/+9
|
* Replace CHUTNEY_PATH with CHUTNEY_BINJim Newsome2024-11-061-2/+0
| | | | | | We no longer need a path to a checkout of the chutney repository; we just need the chutney binary itself. We still allow this to be set explicitly with CHUTNEY_BIN, but fall back to finding it on the PATH.
* CI: bump chutney versionJim Newsome2024-11-061-1/+1
| | | | | This will let us simplify chutney installation, which will be done in a follow-up commit.
* CI python3-checks: Don't install redundant python packagesJim Newsome2024-11-051-1/+1
| | | | | We install recent mypy and flake8 packages from pypy below; we don't need to also install from apt.
* CI: add sections to the rust-recent jobsJim Newsome2024-11-041-0/+13
| | | | | | This will make it a bit easier to look through the output in the gitlab UI, particularly making it easier to see where time is being spent in these long-running jobs.
* integration-shadow; reorganize slightly and ad better section headingsJim Newsome2024-11-041-9/+7
|
* Replace maint/ci_log_span with maint/ci_log_span_fns.shJim Newsome2024-11-041-2/+4
| | | | | | | | | | | Provide functions for starting and ending spans instead of the script doing it itself. The current version of the functions are directly from the gitlab documentation <https://docs.gitlab.com/ee/ci/jobs/job_logs.html#custom-collapsible-sections>. This is currently functionally similar to what was here before, but using functions here will let us make this a bit more convenient, which will be done in a follow-up commit.
* CI: enable timestamps in job log linesJim Newsome2024-11-041-0/+2
| | | | | | This will let us more easily see where time is being spent. https://docs.gitlab.com/ee/ci/jobs/job_logs.html#job-log-timestamps
* CI integration-chutney: install chutney outside of setup scriptJim Newsome2024-10-301-5/+13
| | | | | | | | | | Currently just copy-paste from the integration-chutney-shadow job. This will be simplified and/or folded into an external script pending <https://gitlab.torproject.org/tpo/core/chutney/-/merge_requests/31>. Note that this job is currently disabled, making this commit roughly a no-op. This is just to proactively try to keep this version of the job unbroken for if and when we reenable it.
* CI integration-chutney-shadow: pin chutney versionJim Newsome2024-10-301-1/+10
| | | | | Since chutney is currently under relatively rapid development, let's avoid surprise breakage in arti's CI.
* Merge branch 'python-ci' into 'main'Nick Mathewson2024-10-291-7/+10
|\ | | | | | | | | | | | | CI: Apply flake8, mypy, and black to all of our Python Closes #1689 See merge request tpo/core/arti!2584
| * CI: Re-purpose "python-check" to run python lints.Nick Mathewson2024-10-281-7/+10
| |
* | ci: upload more artifacts in 'integration-chutney-shadow'Steven Engler2024-10-281-0/+5
| | | | | | | | Set "1 week" since I see that it's used on another shadow artifact.
* | integration-chutney-shadow: pip install chutney to get its dependenciesJim Newsome2024-10-281-0/+8
| |
* | .gitlab-ci: reformat long apt-install lineJim Newsome2024-10-281-1/+8
| |
* | ci: use latest shadow commitSteven Engler2024-10-281-2/+3
|/ | | | | The changes in https://github.com/shadow/shadow/pull/3428 should add more details to the CI output of Shadow simulations.
* Make memquota feature part of full in artiIan Jackson2024-10-221-1/+1
| | | | Mark it no longer experimental, but part of full. And document it.
* CI: Append to RUSTFLAGS, in case it's already setIan Jackson2024-10-221-1/+1
| | | | | | | As suggested https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2561#note_3097441 I don't think we can have += since it may not be bash.
* minimal features test: Introduce new --cfg arti_features_preciseIan Jackson2024-10-221-0/+2
| | | | | Work around awkward cargo behaviour and allow us to more reliably test disabled features, even if they're enabled by default at lower levels.
* test-all-crates: conditional options, to test more cratesIan Jackson2024-10-221-1/+1
| | | | | | | | | | | | | This new feature lets us provide the "enable these options which are needed to make the tests pass" featrure, which is different for each of the afflicted crates. Then we can test these crates tor-hsservice arti arti-client which minimal features. This will be important in a moment, as we're going to want to be relying on actually minimal features tests in arti cfg.rs.
* test-all-crates: Introduce proper argument parserIan Jackson2024-10-221-1/+1
|
* shadow tests: Enable and turn on memquotaIan Jackson2024-10-211-1/+1
| | | | This detected the account lifetime bugs fixed in this branch.
* Merge branch 'mq-prevent' into 'main'Ian Jackson2024-10-151-0/+9
|\ | | | | | | | | | | | | Use clippy to prevent non-mq use of mpsc::channel Closes #1659 See merge request tpo/core/arti!2536
| * CI: Add a job to run clippy with different parameters, excluding testsIan Jackson2024-10-151-0/+9
| |
* | Abolish use of python-is-python3Ian Jackson2024-10-151-5/+5
|/ | | | | | | "python" meaning "python3" was a wrongheaded decision by Python upstream. Our python scripts should start (roughly) `#! env python3`. And, this is already the case - we don't actually use python-is-python3!
* Merge branch 'ctor-keystore-shadow' into 'main'gabi-2502024-10-101-1/+1
|\ | | | | | | | | shadow CI: Add a couple of tests involving C Tor keystores See merge request tpo/core/arti!2514
| * shadow CI: Build arti with ctor-keystore support.Gabriela Moldovan2024-10-081-1/+1
| | | | | | | | This is needed to test C Tor keystore support in shadow.
* | CI: run miri on tor-persist tooIan Jackson2024-10-081-1/+1
| |
* | CI: run miri on tor-rtmock tooIan Jackson2024-10-081-1/+1
| |
* | CI: run miri on tor-memquota tooIan Jackson2024-10-081-1/+1
| | | | | | | | | | There's no unsafe in this crate, but it does have some exciting drop bomb stuff.
* | miri: Update the nightly versionIan Jackson2024-10-081-6/+6
| |
* | miri: Fix update runesIan Jackson2024-10-081-2/+2
|/
* Run forbid-hard-tabs in CIIan Jackson2024-10-021-0/+1
|
* CI: run miri, currently on tor-rtcompatIan Jackson2024-09-261-0/+18
| | | | | | I'm about to add some unsafe which I want tested in CI. We must disable two tests.
* Use Rust 1.77 for our reproducible builds.Nick Mathewson2024-09-251-1/+1
|
* Upgrade MSRV to 1.77Nick Mathewson2024-09-251-1/+1
| | | | This will allow us to upgrade to the latest version of rusqlite.
* CI: Only build shadow onceJim Newsome2024-09-181-51/+43
|
* Add ci job `integration-chutney-shadow`Jim Newsome2024-09-181-0/+56
|
* CI: Set up ~/src and ~/.local in before_scriptJim Newsome2024-09-181-5/+6
| | | | | We'll want this in the shadow-chutney test too. No harm in just doing it for all jobs.
* chutney test: rework installation and tracking of chutney itselfJim Newsome2024-09-181-0/+2
| | | | | | | | | | | Previously `tests/chutney/setup` would locate *or install* chutney and set `CHUTNEY_PATH` for itself. However that `CHUTNEY_PATH` wasn't propagated to other steps or "up" to the new `integration-e2e` wrapper script. Tracking it in the arti.run along with other dynamic info lets us ensure we consistently use the same chutney across steps, and in the higher level `integration-e2e` script.