summaryrefslogtreecommitdiff
path: root/git-reset-script
diff options
context:
space:
mode:
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>2022-05-12 22:39:40 (GMT)
committerJunio C Hamano <gitster@pobox.com>2022-05-12 22:43:08 (GMT)
commitf15e00b463b4dceaf5b260883975e93c24581b2c (patch)
treefb1405c2b2901aeb15046cb497b5a2e4f351465b /git-reset-script
parent49af4481973d14d9cae1abb61e44f1567369cd65 (diff)
downloadgit-f15e00b463b4dceaf5b260883975e93c24581b2c.zip
git-f15e00b463b4dceaf5b260883975e93c24581b2c.tar.gz
git-f15e00b463b4dceaf5b260883975e93c24581b2c.tar.bz2
ci: use https, not http to download binaries from perforce.com
Since 522354d70f4 (Add Travis CI support, 2015-11-27) the CI has used http://filehost.perforce.com/perforce/ to download binaries from filehost.perforce.com, they were then moved to this script in 657343a602e (travis-ci: move Travis CI code into dedicated scripts, 2017-09-10). Let's use https instead for good measure. I don't think we need to worry about the DNS or network between the GitHub CI and perforce.com being MitM'd, but using https gives us extra validation of the payload at least, and is one less thing to worry about when checking where else we rely on non-TLS'd http connections. Also, use the same download site at perforce.com for Linux and macOS tarballs for consistency. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Carlo Marcelo Arenas Belón <carenas@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-reset-script')
0 files changed, 0 insertions, 0 deletions