mirror of https://github.com/zulip/zulip.git
65 lines
2.7 KiB
Bash
Executable File
65 lines
2.7 KiB
Bash
Executable File
#!/bin/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.
|
|
#
|
|
# This script is more complicated than that, basically because Travis
|
|
# CI installs a ton of crap in its build workers, and we need to
|
|
# remove some and reconfigure others to make things run smoothly and
|
|
# quickly.
|
|
#
|
|
# More description in https://zulip.readthedocs.io/en/latest/testing/travis.html.
|
|
set -e
|
|
set -x
|
|
|
|
# Make /home/travis world-readable so the `zulip` user will be able to
|
|
# read it, since that's where we store our caches.
|
|
sudo chmod a+rX /home/travis
|
|
|
|
# Uninstall the unnecessary extra versions of postgres that Travis CI
|
|
# installs since if we don't do this, doing apt upgrades can fail due
|
|
# to conflicts over which version of postgres should be running.
|
|
sudo apt-get remove postgresql-9.2 postgresql-client-9.2 postgresql-contrib-9.2 postgresql-9.4 postgresql-client-9.4 postgresql-9.5 postgresql-contrib-9.5 postgresql-client-9.5 postgresql-9.6 postgresql-contrib-9.6 postgresql-client-9.6 -y
|
|
|
|
# Remove some of Travis's' stupid extra sources.list files
|
|
sudo rm -f /etc/apt/sources.list.d/mongodb*.list
|
|
|
|
# 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.
|
|
if ! tools/provision --production-travis; then
|
|
echo "\`provision\`: Something went wrong with the provisioning, might be a network issue, Retrying to provision..."
|
|
tools/provision --production-travis
|
|
fi
|
|
|
|
cp -a tools/travis/success-http-headers.txt ~/
|
|
source tools/travis/activate-venv
|
|
|
|
# Force OpenJDK 8 JRE. This is a workaround for Travis CI having
|
|
# broken their java install, but also nicely provides consistency.
|
|
sudo ln -nsf /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java /usr/bin/java
|
|
|
|
if ! env TRAVIS=1 ./tools/build-release-tarball travis; then
|
|
echo "Attempting to output failure logging data"
|
|
cat /tmp/tmp.*/update-prod-static.log || true
|
|
exit 1
|
|
fi
|
|
mv /tmp/tmp.*/zulip-server-travis.tar.gz ./
|
|
|
|
|
|
# Shut down all services so that restarting postgres and rebuilding
|
|
# the postgres database to match the prod installation setup will work.
|
|
sudo supervisorctl stop all
|
|
# Clear memcached to avoid contamination between development and prod
|
|
# environments.
|
|
sudo /etc/init.d/memcached restart
|
|
|
|
# Drop any open connections to the development postgres installation.
|
|
sudo "$(dirname "$0")/../../scripts/setup/terminate-psql-sessions" postgres zulip zulip_base
|
|
|
|
# Remove and recreate the postgres database
|
|
sudo pg_ctlcluster 9.3 main stop
|
|
sudo pg_dropcluster 9.3 main
|
|
sudo rm -rf /etc/postgresql/9.3/main /var/lib/postgresql/9.3/main
|
|
sudo pg_createcluster 9.3 main
|