mirrors/arti.git/.gitlab-ci.yml, branch arti-v0.4.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0 2022-05-26T12:53:14Z Merge branch 'standardise-shell' into 'main' 2022-05-26T12:53:14Z Nick Mathewson nickm@torproject.org 2022-05-26T12:53:14Z urn:sha1:68b04197528896bf84774c738cf6439e73977c5e Standardise shell Closes #425 See merge request tpo/core/arti!533 make almost all scripts use bash and set euo pipefail 2022-05-25T20:25:58Z trinity-1686a trinity@deuxfleurs.fr 2022-05-25T11:10:55Z urn:sha1:8eb843f2af349e4dbbd377a4c16fa57094c90414 ci: set umask instead of ARTI_FS_DISABLE_PERMISSION_CHECKS 2022-05-25T14:27:45Z Alex Xu (Hello71) alex_y_xu@yahoo.ca 2022-05-24T15:10:45Z urn:sha1:4797c120d0454ce42553d949da2426f99af110ac Update Gitlab CI config for Gitlab 14.10 2022-05-23T10:14:09Z eta tor@eta.st 2022-05-23T10:14:09Z urn:sha1:b137d64e181c579a5bc06e28ab75f6dc0c100fd7 see https://gitlab.com/gitlab-org/gitlab/-/issues/344533 Disable fs-mistrust in coverage CI. 2022-05-10T12:14:13Z Nick Mathewson nickm@torproject.org 2022-05-10T12:14:13Z urn:sha1:78e86e6b819c231089886ff59fbe32f5a190948f The CI runners like to run as root with umask 000, which our code rightly freaks out about. Merge branch 'use-fs-mistrust' 2022-05-09T19:27:25Z Nick Mathewson nickm@torproject.org 2022-05-09T19:27:25Z urn:sha1:4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3 only deploy pages on main 2022-05-05T20:21:09Z trinity-1686a trinity@deuxfleurs.fr 2022-05-05T20:21:09Z urn:sha1:98de5cff3c4cd5b02811741e6d051d2353895e90 add schedulable job to generate aggregated coverage 2022-05-05T19:05:42Z trinity-1686a trinity@deuxfleurs.fr 2022-05-05T11:52:00Z urn:sha1:9ed5983c7647082579f6b037575e498f1cc5f479 gitlab-ci: Disable fs mistrust in integration test 2022-05-05T13:47:13Z Nick Mathewson nickm@torproject.org 2022-05-04T12:45:47Z urn:sha1:b9c54af707d1db9165bed83223ce48652633d460 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. CI: Check that the lockfile is up to date. 2022-05-04T13:31:20Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-04T12:43:34Z urn:sha1:875f3e4352c684c8758863820c09d81641f55737 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.