mirror of
https://github.com/zulip/zulip.git
synced 2026-07-03 21:10:12 +08:00
`check_version` in `install-yarn` had the rather careful check that the yarn it installed into `/usr/bin/yarn` was the yarn which was first in the user's `$PATH`. This caused problems when the user had a pre-existing `/usr/local/bin/yarn`; however, those problems are limited to the `install-yarn` script itself, since the nearly all calls to yarn from Zulip's code already hardcode the `/srv/zulip-yarn` location, and do not depend on what is in `$PATH`. Remove the checks in `install-yarn` that depend on the local `$PATH`, and stop installing our `yarn` into it. We also adjust the two callsites which did not specify the full path to `yarn`, so use `/srv/zulip-yarn`. Fixes: #23993 Co-authored-by: Alex Vandiver <alexmv@zulip.com>
54 lines
2.0 KiB
Bash
Executable File
54 lines
2.0 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/production-install \
|
|
tools/ci/production-verify \
|
|
tools/ci/production-upgrade \
|
|
tools/ci/production-pgroonga \
|
|
tools/ci/production-upgrade-pg \
|
|
tools/ci/generate-failure-message \
|
|
package.json yarn.lock \
|
|
/tmp/production-build
|
|
|
|
# Check that webpack bundles use only ES2019 syntax.
|
|
# Use the yarn binary installed by tools/provision.
|
|
YARN="/srv/zulip-yarn/bin/yarn"
|
|
tar -C /tmp -xzf /tmp/production-build/zulip-server-test.tar.gz zulip-server-test/prod-static/serve/webpack-bundles
|
|
(
|
|
GLOBIGNORE=/tmp/zulip-server-test/prod-static/serve/webpack-bundles/katex-cli.js
|
|
$YARN run es-check es2019 /tmp/zulip-server-test/prod-static/serve/webpack-bundles/*.js
|
|
)
|