mirrors/arti.git/.gitlab-ci.yml, branch arti-v1.1.10 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10 2023-10-13T16:37:03Z remove artifact generation from rust-latest-test-all-features 2023-10-13T16:37:03Z trinity-1686a trinity@deuxfleurs.fr 2023-10-13T16:37:03Z urn:sha1:2a7aa162e31e138b8bd77b76a0be943f429dba9e move usage of ./maint/preserve out of after_script 2023-10-13T16:17:00Z trinity-1686a trinity@deuxfleurs.fr 2023-10-13T16:11:10Z urn:sha1:9e49b8aa3b5427bafcd29da6749caae5ec38ad43 CI: Remove amd64 tags 2023-09-18T13:42:58Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-09-18T13:42:58Z urn:sha1:f300fe459bb9674d26fd34f56c016794adfcb008 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 tests 2023-09-05T13:20:47Z Jim Newsome jnewsome@torproject.org 2023-09-05T13:20:47Z urn:sha1:acf87aa13a969fdab957fd193824f078971757bf CI: Ensure libsqlite3 is installed in shadow and chutney tests 2023-09-05T13:07:00Z Jim Newsome jnewsome@torproject.org 2023-09-05T13:07:00Z urn:sha1:63351fc1d6c0e4451b1c37f5f5fbab0ac7c430be Update CI to use Debian bookworm instead of bullseye 2023-08-29T14:08:41Z Jim Newsome jnewsome@torproject.org 2023-08-25T19:16:33Z urn:sha1:95067549c6548023929144b0505ade71907274bf shadow test: use libigraph from bullseye 2023-08-29T14:08:37Z Jim Newsome jnewsome@torproject.org 2023-08-25T21:42:42Z urn:sha1:26ac5eea78b5c513349db8edadb0b192138d9359 Workaround for https://github.com/shadow/tgen/issues/44 CI: Replace all uses of `debian:stable-slim` with `bookworm` 2023-08-25T16:29:31Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-08-25T15:48:51Z urn:sha1:4a9724733b3fe470eaecdb2ab9e6c83e0cf99a8a 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` 2023-08-25T16:29:23Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-08-25T15:42:04Z urn:sha1:7f70ab83c3ebeea91f0d33e1f24167a9ded8093a `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-image 2023-08-25T16:28:16Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-08-25T15:59:04Z urn:sha1:f45e53b15f0fd142a5403ed58af6a4a471f0fbf4 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.