2017-09-10 16:44:28 +02:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
#
|
|
|
|
# Install dependencies required to build and test Git on Linux and macOS
|
|
|
|
#
|
|
|
|
|
2019-01-28 00:26:50 +01:00
|
|
|
. ${0%/*}/lib.sh
|
2017-09-10 16:44:28 +02:00
|
|
|
|
2017-09-11 03:18:29 +02:00
|
|
|
P4WHENCE=http://filehost.perforce.com/perforce/r$LINUX_P4_VERSION
|
|
|
|
LFSWHENCE=https://github.com/github/git-lfs/releases/download/v$LINUX_GIT_LFS_VERSION
|
2020-04-10 19:18:07 +02:00
|
|
|
UBUNTU_COMMON_PKGS="make libssl-dev libcurl4-openssl-dev libexpat-dev
|
|
|
|
tcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl
|
|
|
|
libemail-valid-perl libio-socket-ssl-perl libnet-smtp-ssl-perl"
|
2017-09-11 03:18:29 +02:00
|
|
|
|
2021-11-23 17:29:11 +01:00
|
|
|
case "$runs_on_pool" in
|
|
|
|
ubuntu-latest)
|
2018-11-01 12:47:14 +01:00
|
|
|
sudo apt-get -q update
|
2020-04-10 19:18:07 +02:00
|
|
|
sudo apt-get -q -y install language-pack-is libsvn-perl apache2 \
|
2021-11-23 17:29:11 +01:00
|
|
|
$UBUNTU_COMMON_PKGS $CC_PACKAGE
|
travis-ci: fix running P4 and Git LFS tests in Linux build jobs
Linux build jobs on Travis CI skip the P4 and Git LFS tests since
commit 657343a60 (travis-ci: move Travis CI code into dedicated
scripts, 2017-09-10), claiming there are no P4 or Git LFS installed.
The reason is that P4 and Git LFS binaries are not installed to a
directory in the default $PATH, but their directories are prepended to
$PATH. This worked just fine before said commit, because $PATH was
set in a scriptlet embedded in our '.travis.yml', thus its new value
was visible during the rest of the build job. However, after these
embedded scriptlets were moved into dedicated scripts executed in
separate shell processes, any variable set in one of those scripts is
only visible in that single script but not in any of the others. In
this case, 'ci/install-dependencies.sh' downloads P4 and Git LFS and
modifies $PATH, but to no effect, because 'ci/run-tests.sh' only sees
Travis CI's default $PATH.
Move adjusting $PATH to 'ci/lib-travisci.sh', which is sourced in all
other 'ci/' scripts, so all those scripts will see the updated $PATH
value.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-11-01 12:55:35 +01:00
|
|
|
mkdir --parents "$P4_PATH"
|
|
|
|
pushd "$P4_PATH"
|
2017-09-11 03:18:29 +02:00
|
|
|
wget --quiet "$P4WHENCE/bin.linux26x86_64/p4d"
|
|
|
|
wget --quiet "$P4WHENCE/bin.linux26x86_64/p4"
|
|
|
|
chmod u+x p4d
|
|
|
|
chmod u+x p4
|
|
|
|
popd
|
travis-ci: fix running P4 and Git LFS tests in Linux build jobs
Linux build jobs on Travis CI skip the P4 and Git LFS tests since
commit 657343a60 (travis-ci: move Travis CI code into dedicated
scripts, 2017-09-10), claiming there are no P4 or Git LFS installed.
The reason is that P4 and Git LFS binaries are not installed to a
directory in the default $PATH, but their directories are prepended to
$PATH. This worked just fine before said commit, because $PATH was
set in a scriptlet embedded in our '.travis.yml', thus its new value
was visible during the rest of the build job. However, after these
embedded scriptlets were moved into dedicated scripts executed in
separate shell processes, any variable set in one of those scripts is
only visible in that single script but not in any of the others. In
this case, 'ci/install-dependencies.sh' downloads P4 and Git LFS and
modifies $PATH, but to no effect, because 'ci/run-tests.sh' only sees
Travis CI's default $PATH.
Move adjusting $PATH to 'ci/lib-travisci.sh', which is sourced in all
other 'ci/' scripts, so all those scripts will see the updated $PATH
value.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-11-01 12:55:35 +01:00
|
|
|
mkdir --parents "$GIT_LFS_PATH"
|
|
|
|
pushd "$GIT_LFS_PATH"
|
2017-09-11 03:18:29 +02:00
|
|
|
wget --quiet "$LFSWHENCE/git-lfs-linux-amd64-$LINUX_GIT_LFS_VERSION.tar.gz"
|
|
|
|
tar --extract --gunzip --file "git-lfs-linux-amd64-$LINUX_GIT_LFS_VERSION.tar.gz"
|
|
|
|
cp git-lfs-$LINUX_GIT_LFS_VERSION/git-lfs .
|
|
|
|
popd
|
2017-09-10 16:44:28 +02:00
|
|
|
;;
|
2021-11-23 17:29:11 +01:00
|
|
|
macos-latest)
|
2019-07-03 12:47:48 +02:00
|
|
|
export HOMEBREW_NO_AUTO_UPDATE=1 HOMEBREW_NO_INSTALL_CLEANUP=1
|
2017-09-11 03:18:29 +02:00
|
|
|
# Uncomment this if you want to run perf tests:
|
|
|
|
# brew install gnu-time
|
ci/lib.sh: encapsulate Travis-specific things
The upcoming patches will allow building git.git via Azure Pipelines
(i.e. Azure DevOps' Continuous Integration), where variable names and
URLs look a bit different than in Travis CI.
Also, the configurations of the available agents are different. For
example, Travis' and Azure Pipelines' macOS agents are set up
differently, so that on Travis, we have to install the git-lfs and
gettext Homebrew packages, and on Azure Pipelines we do not need to.
Likewise, Azure Pipelines' Ubuntu agents already have asciidoctor
installed.
Finally, on Azure Pipelines the natural way is not to base64-encode tar
files of the trash directories of failed tests, but to publish build
artifacts instead. Therefore, that code to log those base64-encoded tar
files is guarded to be Travis-specific.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-01-28 00:26:51 +01:00
|
|
|
test -z "$BREW_INSTALL_PACKAGES" ||
|
|
|
|
brew install $BREW_INSTALL_PACKAGES
|
2017-09-11 03:18:29 +02:00
|
|
|
brew link --force gettext
|
2021-01-15 03:51:02 +01:00
|
|
|
brew install --cask --no-quarantine perforce || {
|
ci(osx): use new location of the `perforce` cask
The Azure Pipelines builds are failing for macOS due to a change in the
location of the perforce cask. The command outputs the following error:
+ brew install caskroom/cask/perforce
Error: caskroom/cask was moved. Tap homebrew/cask-cask instead.
So let's try to call `brew cask install perforce` first (which is what
that error message suggests, in a most round-about way).
Prior to 672f51cb we used to install the 'perforce' package with 'brew
install perforce' (note: no 'cask' in there). The justification for
672f51cb was that the command 'brew install perforce' simply stopped
working, after Homebrew folks decided that it's better to move the
'perforce' package to a "cask". Their justification for this move was
that 'brew install perforce' "can fail due to a checksum mismatch ...",
and casks can be installed without checksum verification. And indeed,
both 'brew cask install perforce' and 'brew install
caskroom/cask/perforce' printed something along the lines of:
==> No checksum defined for Cask perforce, skipping verification
It is unclear why 672f51cb used 'brew install caskroom/cask/perforce'
instead of 'brew cask install perforce'. It appears (by running both
commands on old Travis CI macOS images) that both commands worked all
the same already back then.
In any case, as the error message at the top of this commit message
shows, 'brew install caskroom/cask/perforce' has stopped working
recently, but 'brew cask install perforce' still does, so let's use
that.
CI servers are typically fresh virtual machines, but not always. To
accommodate for that, let's try harder if `brew cask install perforce`
fails, by specifically pulling the latest `master` of the
`homebrew-cask` repository.
This will still fail, of course, when `homebrew-cask` falls behind
Perforce's release schedule. But once it is updated, we can now simply
re-run the failed jobs and they will pick up that update.
As for updating `homebrew-cask`: the beginnings of automating this in
https://dev.azure.com/gitgitgadget/git/_build?definitionId=11&_a=summary
will be finished once the next Perforce upgrade comes around.
Helped-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-10-23 02:19:38 +02:00
|
|
|
# Update the definitions and try again
|
2019-11-20 02:18:39 +01:00
|
|
|
cask_repo="$(brew --repository)"/Library/Taps/homebrew/homebrew-cask &&
|
2021-01-15 03:51:02 +01:00
|
|
|
git -C "$cask_repo" pull --no-stat --ff-only &&
|
|
|
|
brew install --cask --no-quarantine perforce
|
ci(osx): use new location of the `perforce` cask
The Azure Pipelines builds are failing for macOS due to a change in the
location of the perforce cask. The command outputs the following error:
+ brew install caskroom/cask/perforce
Error: caskroom/cask was moved. Tap homebrew/cask-cask instead.
So let's try to call `brew cask install perforce` first (which is what
that error message suggests, in a most round-about way).
Prior to 672f51cb we used to install the 'perforce' package with 'brew
install perforce' (note: no 'cask' in there). The justification for
672f51cb was that the command 'brew install perforce' simply stopped
working, after Homebrew folks decided that it's better to move the
'perforce' package to a "cask". Their justification for this move was
that 'brew install perforce' "can fail due to a checksum mismatch ...",
and casks can be installed without checksum verification. And indeed,
both 'brew cask install perforce' and 'brew install
caskroom/cask/perforce' printed something along the lines of:
==> No checksum defined for Cask perforce, skipping verification
It is unclear why 672f51cb used 'brew install caskroom/cask/perforce'
instead of 'brew cask install perforce'. It appears (by running both
commands on old Travis CI macOS images) that both commands worked all
the same already back then.
In any case, as the error message at the top of this commit message
shows, 'brew install caskroom/cask/perforce' has stopped working
recently, but 'brew cask install perforce' still does, so let's use
that.
CI servers are typically fresh virtual machines, but not always. To
accommodate for that, let's try harder if `brew cask install perforce`
fails, by specifically pulling the latest `master` of the
`homebrew-cask` repository.
This will still fail, of course, when `homebrew-cask` falls behind
Perforce's release schedule. But once it is updated, we can now simply
re-run the failed jobs and they will pick up that update.
As for updating `homebrew-cask`: the beginnings of automating this in
https://dev.azure.com/gitgitgadget/git/_build?definitionId=11&_a=summary
will be finished once the next Perforce upgrade comes around.
Helped-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-10-23 02:19:38 +02:00
|
|
|
} ||
|
2021-01-15 03:51:02 +01:00
|
|
|
brew install homebrew/cask/perforce
|
2021-11-23 17:29:11 +01:00
|
|
|
|
|
|
|
if test -n "$CC_PACKAGE"
|
|
|
|
then
|
|
|
|
BREW_PACKAGE=${CC_PACKAGE/-/@}
|
|
|
|
brew install "$BREW_PACKAGE"
|
|
|
|
brew link "$BREW_PACKAGE"
|
|
|
|
fi
|
2017-09-10 16:44:28 +02:00
|
|
|
;;
|
2021-11-23 17:29:11 +01:00
|
|
|
esac
|
|
|
|
|
|
|
|
case "$jobname" in
|
2018-11-01 12:47:14 +01:00
|
|
|
StaticAnalysis)
|
|
|
|
sudo apt-get -q update
|
2019-10-01 13:16:26 +02:00
|
|
|
sudo apt-get -q -y install coccinelle libcurl4-openssl-dev libssl-dev \
|
2020-04-10 19:18:07 +02:00
|
|
|
libexpat-dev gettext make
|
2018-11-01 12:47:14 +01:00
|
|
|
;;
|
2021-07-26 20:22:27 +02:00
|
|
|
sparse)
|
|
|
|
sudo apt-get -q update -q
|
|
|
|
sudo apt-get -q -y install libssl-dev libcurl4-openssl-dev \
|
|
|
|
libexpat-dev gettext zlib1g-dev
|
|
|
|
;;
|
2018-11-01 12:47:14 +01:00
|
|
|
Documentation)
|
|
|
|
sudo apt-get -q update
|
2020-04-10 19:18:07 +02:00
|
|
|
sudo apt-get -q -y install asciidoc xmlto docbook-xsl-ns make
|
2019-03-29 13:35:18 +01:00
|
|
|
|
|
|
|
test -n "$ALREADY_HAVE_ASCIIDOCTOR" ||
|
2020-04-10 19:18:08 +02:00
|
|
|
sudo gem install --version 1.5.8 asciidoctor
|
2018-11-01 12:47:14 +01:00
|
|
|
;;
|
2021-11-23 17:29:08 +01:00
|
|
|
linux-gcc-default)
|
2020-04-10 19:18:07 +02:00
|
|
|
sudo apt-get -q update
|
|
|
|
sudo apt-get -q -y install $UBUNTU_COMMON_PKGS
|
|
|
|
;;
|
2017-09-10 16:44:28 +02:00
|
|
|
esac
|
|
|
|
|
2022-05-13 00:39:37 +02:00
|
|
|
if type p4d >/dev/null 2>&1 && type p4 >/dev/null 2>&1
|
2018-11-01 12:47:14 +01:00
|
|
|
then
|
|
|
|
echo "$(tput setaf 6)Perforce Server Version$(tput sgr0)"
|
|
|
|
p4d -V | grep Rev.
|
|
|
|
echo "$(tput setaf 6)Perforce Client Version$(tput sgr0)"
|
|
|
|
p4 -V | grep Rev.
|
2022-05-13 00:39:37 +02:00
|
|
|
else
|
|
|
|
echo >&2 "WARNING: perforce wasn't installed, see above for clues why"
|
2018-11-01 12:47:14 +01:00
|
|
|
fi
|
2022-05-13 00:39:37 +02:00
|
|
|
if type git-lfs >/dev/null 2>&1
|
2018-11-01 12:47:14 +01:00
|
|
|
then
|
|
|
|
echo "$(tput setaf 6)Git-LFS Version$(tput sgr0)"
|
|
|
|
git-lfs version
|
2022-05-13 00:39:37 +02:00
|
|
|
else
|
|
|
|
echo >&2 "WARNING: git-lfs wasn't installed, see above for clues why"
|
2018-11-01 12:47:14 +01:00
|
|
|
fi
|