git/ci at bda957de7cd86933aa898351c796fd4a7d18f983 - git

mirror of https://github.com/git/git.git synced 2026-01-22 06:47:19 +09:00

History

Junio C Hamano 1ad5c3df35 ci: use DC_SHA1=YesPlease on osx-clang job for CI

7b8cfe34 (Merge branch 'ed/fsmonitor-on-networked-macos',
2022-10-17) broke the build on macOS with sha1dc by bypassing our
hash abstraction (git_SHA_CTX etc.), but it wasn't caught before the
problematic topic was merged down to the 'master' branch.  Nobody
was even compile testing with DC_SHA1 set, although it is the
recommended choice in these days for folks when they use SHA-1.

This was because the default for macOS uses Apple Common Crypto, and
both of the two CI jobs did not override the default.  Tweak one of
them to use DC_SHA1 to improve the coverage.

We may want to give similar diversity for Linux jobs so that some of
them build with other implementations of SHA-1; they currently all
build and test with DC_SHA1 as that is the default on everywhere
other than macOS.

But let's start small to fill only the immediate need.

Signed-off-by: Junio C Hamano <gitster@pobox.com>

2022-10-20 10:01:37 -07:00

config

ci/config: correct instruction for CI preferences

2020-05-18 10:18:34 -07:00

util

travis-ci: include the trash directories of failed tests in the trace log

2018-08-01 09:59:36 -07:00

check-directional-formatting.bash

ci: disallow directional formatting

2021-11-04 10:13:10 -07:00

install-dependencies.sh

ci: use https, not http to download binaries from perforce.com