Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
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 pnpm-lock.yaml \
|
|
/tmp/production-build
|
|
|
|
# Check that webpack bundles use only ES2022 syntax.
|
|
# Use the pnpm binary installed by tools/provision.
|
|
PNPM="/usr/local/bin/pnpm"
|
|
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*.js"
|
|
"$PNPM" exec es-check es2022 /tmp/zulip-server-test/prod-static/serve/webpack-bundles/*.js
|
|
)
|