Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/travis/setup-production

31 lines
1.3 KiB
Plaintext
Raw Normal View History

Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work.
2015-10-15 01:47:42 +02:00
#!/bin/bash
set -e
set -x
Fix postgres errors in Travis CI again. Travis CI's model of installing every version of postgres on the test VM and then shutting all the versions other than the one requested down seems to not work very well with doing apt upgrades. It seems the best way to resolve this is to just uninstall the versions we don't need.
2016-01-19 20:44:21 +01:00
# 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.
setup-production: Remove more irrelevant postgres packages.
2016-06-22 17:57:06 +02:00
sudo apt-get remove postgresql-9.1 postgresql-client-9.1 postgresql-9.1-postgis-2.2 postgresql-contrib-9.1 postgresql-9.2 postgresql-client-9.2 postgresql-9.2-postgis-2.2 postgresql-contrib-9.2 postgresql-9.4 -y
Fix postgres errors in Travis CI again. Travis CI's model of installing every version of postgres on the test VM and then shutting all the versions other than the one requested down seems to not work very well with doing apt upgrades. It seems the best way to resolve this is to just uninstall the versions we don't need.
2016-01-19 20:44:21 +01:00
Move provision.py under tools/.
2016-06-27 23:50:38 +02:00
python tools/provision.py --travis --production-travis
travis: Verify the server doesn't 500 in production test.
2016-05-08 03:19:48 +02:00
cp -a tools/travis/success-http-headers.txt ~/
Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work.
2015-10-15 01:47:42 +02:00
source /srv/zulip-venv/bin/activate
./tools/build-release-tarball travis
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