df821f35ee
The jenkins-common script is the better place for this particular setup, since that script is doing similar setup steps to prepare the environment for running various tests/subsequent scripts. This also will resolve downstream processes, such as our jenkins AMI builder (for jenkins-worker images).
40 lines
1.2 KiB
Bash
40 lines
1.2 KiB
Bash
#!/usr/bin/env bash
|
|
|
|
source $HOME/jenkins_env
|
|
|
|
# Clear the mongo database
|
|
# Note that this prevents us from running jobs in parallel on a single worker.
|
|
mongo --quiet --eval 'db.getMongo().getDBNames().forEach(function(i){db.getSiblingDB(i).dropDatabase()})'
|
|
|
|
# Ensure we have fetched origin/master
|
|
# Some of the reporting tools compare the checked out branch to origin/master;
|
|
# depending on how the GitHub plugin refspec is configured, this may
|
|
# not already be fetched.
|
|
git fetch origin master:refs/remotes/origin/master
|
|
|
|
# Reset the jenkins worker's ruby environment back to
|
|
# the state it was in when the instance was spun up.
|
|
if [ -e $HOME/edx-rbenv_clean.tar.gz ]; then
|
|
rm -rf $HOME/.rbenv
|
|
tar -C $HOME -xf $HOME/edx-rbenv_clean.tar.gz
|
|
fi
|
|
|
|
# Bootstrap Ruby requirements so we can run the tests
|
|
bundle install
|
|
|
|
# Ensure the Ruby environment contains no stray gems
|
|
bundle clean --force
|
|
|
|
# Reset the jenkins worker's virtualenv back to the
|
|
# state it was in when the instance was spun up.
|
|
if [ -e $HOME/edx-venv_clean.tar.gz ]; then
|
|
rm -rf $HOME/edx-venv
|
|
tar -C $HOME -xf $HOME/edx-venv_clean.tar.gz
|
|
fi
|
|
|
|
# Activate the Python virtualenv
|
|
source $HOME/edx-venv/bin/activate
|
|
|
|
# add the node_js packages dir to PATH
|
|
PATH=$PATH:node_modules/.bin
|