mirror of
https://github.com/zulip/zulip.git
synced 2025-11-02 21:13:36 +00:00
371cdf9dc1
We support Debian as an OS for setting up the Zulip server. But the CI does not run on pull request to test the setting up of the server on Debian. Hence, add the check to CI.
46 lines
1.6 KiB
Bash
Executable File
46 lines
1.6 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# In short, this provisions a Zulip development environment and then
|
|
# builds a Zulip release tarball (the same way we build them for an
|
|
# actual release). The actual test job will then install that.
|
|
|
|
set -e
|
|
set -x
|
|
|
|
# Provisioning may fail due to many issues but most of the times a network
|
|
# connection issue is the reason. So we are going to retry entire provisioning
|
|
# once again if that fixes our problem.
|
|
tools/provision --build-release-tarball-only || {
|
|
ret=$?
|
|
if [ "$ret" = 1 ]; then
|
|
echo "\`provision\`: Something went wrong with the provisioning, might be a network issue, Retrying to provision..."
|
|
tools/provision --build-release-tarball-only
|
|
else
|
|
echo "\`provision\`: Something REALLY BAD went wrong with the provisioning, not retrying."
|
|
exit "$ret"
|
|
fi
|
|
}
|
|
|
|
source tools/ci/activate-venv
|
|
|
|
if ! ./tools/build-release-tarball test; then
|
|
echo "Attempting to output failure logging data"
|
|
cat /tmp/tmp.*/update-prod-static.log || true
|
|
exit 1
|
|
fi
|
|
|
|
# Move all the required artifacts to /tmp/production-build
|
|
# that will be later sent down to downstream install jobs.
|
|
mkdir /tmp/production-build
|
|
mv /tmp/tmp.*/zulip-server-test.tar.gz /tmp/production-build
|
|
cp -a \
|
|
tools/ci/success-http-headers.template.txt \
|
|
tools/ci/success-http-headers.template.debian.txt \
|
|
tools/ci/production-install \
|
|
tools/ci/production-verify \
|
|
tools/ci/production-upgrade-pg \
|
|
tools/ci/production-extract-tarball \
|
|
tools/ci/send-failure-message \
|
|
package.json yarn.lock \
|
|
\
|
|
/tmp/production-build
|