CI: use a fixed version of chutney

While chutney currently runs tor's chutney test in its own CI,
it's difficult to guarantee the two won't accidentally diverge.
Probably best to use a fixed version here so that we can control
chutney version bumps and avoid surprise breakage in tor's CI.

This will also free us to intentionally make breaking changes in
chutney (though I don't have any immediate plans for any).
This commit is contained in:
Jim Newsome 2024-10-30 10:34:58 -05:00
parent 3abcb33545
commit f79a5e6629
2 changed files with 9 additions and 1 deletions

View File

@ -108,7 +108,12 @@ variables:
# TODO: This next line should not be debian-only.
- |
if [ "$CHUTNEY" = yes ]; then
git clone --depth 1 https://gitlab.torproject.org/tpo/core/chutney.git
# Use a fixed version of chutney to avoid surprise breakage.
CHUTNEY_SHALLOW_SINCE=2024-10-28
CHUTNEY_COMMIT=be881a1e7c4bc8038fa13fde4a7b24e5c56349c4
git clone --shallow-since "$CHUTNEY_SHALLOW_SINCE" https://gitlab.torproject.org/tpo/core/chutney.git
git -C ./chutney checkout "$CHUTNEY_COMMIT"
export CHUTNEY_PATH="$(pwd)/chutney"
# Have pip install chutney's python dependencies by installing chutney
# itself.

3
changes/ci-pin-chutney Normal file
View File

@ -0,0 +1,3 @@
o Minor feature (testing, CI):
- Use a fixed version of chutney (be881a1e) instead of its current HEAD.
This version should also be preferred when testing locally.