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

13 lines
440 B
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
Add wrapper and log file output for provisioning. Before this commit, provisioning was done by executing provision.py, which printed the log directly to stdout, making debugging harder. This commit creates a wrapper bash script 'provision' in tools, which calls 'zulip/scripts/tools/provision_vm.py' (the new location of provision.py) and prints all the output to 'zulip/var/log/zulip/zulip_provision.log' via 'tee'. Travis tests and docs have been modified accordingly.
2017-01-14 11:19:26 +01:00
docs: Add a bunch of documentation on Travis CI.
2017-06-06 03:15:17 +02:00
# This is just a thin wrapper around provision.
setup-backend: Add wrapper to retry provisioning in case it fails. In this commit we add a wrapper around the provisioning inside setup-backend to trigger another try at provisioning if it fails in hopes of it will run this time fine if it was interuppted by a network issue the first time. Fixes: #2034.
2017-06-13 22:00:11 +02:00
# 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.
travis/setup-backend: Remove the '--travis' flag in tools/provision. Whether the env is Travis or not, this has been detected via $TRAVIS env var. Proof: https://github.com/zulip/zulip/blob/6fbf41bdbc960ab7af81123b81b8aea71113359a/tools/provision#L38
2017-10-06 08:12:16 +02:00
if ! tools/provision; then
setup-backend: Add wrapper to retry provisioning in case it fails. In this commit we add a wrapper around the provisioning inside setup-backend to trigger another try at provisioning if it fails in hopes of it will run this time fine if it was interuppted by a network issue the first time. Fixes: #2034.
2017-06-13 22:00:11 +02:00
echo "\`provision\`: Something went wrong with the provisioning, might be a network issue, Retrying to provision..."
travis/setup-backend: Remove the '--travis' flag in tools/provision. Whether the env is Travis or not, this has been detected via $TRAVIS env var. Proof: https://github.com/zulip/zulip/blob/6fbf41bdbc960ab7af81123b81b8aea71113359a/tools/provision#L38
2017-10-06 08:12:16 +02:00
tools/provision
setup-backend: Add wrapper to retry provisioning in case it fails. In this commit we add a wrapper around the provisioning inside setup-backend to trigger another try at provisioning if it fails in hopes of it will run this time fine if it was interuppted by a network issue the first time. Fixes: #2034.
2017-06-13 22:00:11 +02:00
fi