Monty Taylor 7da7d559ee Update projects when requirements change
Waiting for projects to catch up with requirements versions winds up
with us in a period where everything is out of whack. Instead, everytime
we update the requirements, we should just submit changes that update
everything.

Change-Id: I93465255c27fb2079915c7b3cd9170bfc40b8c35
2013-09-26 13:36:10 -04:00

37 lines
1.1 KiB
YAML

- job:
name: gate-requirements-install
node: precise
builders:
- gerrit-git-prep
- shell: |
#!/bin/bash -xe
source /usr/local/jenkins/slave_scripts/select-mirror.sh openstack requirements
virtualenv --clear .venv
FILE="global-requirements.txt"
# Ignore lines beginning with https?:// just as the mirror script does.
sed -e '/^https\?:\/\//d' $FILE > $FILE.clean
# Run the same basic pip command that the mirror script runs.
.venv/bin/pip install -M -U --exists-action=w -r $FILE.clean
if [ -e dev-requirements.txt ] ; then
.venv/bin/pip install -M -U --exists-action=w -r dev-requirements.txt
fi
# Print all installed stuff to demonstrate versions
.venv/bin/pip freeze
publishers:
- console-log
- job:
name: propose-requirements-updates
node: proposal
builders:
- gerrit-git-prep
- shell: /usr/local/jenkins/slave_scripts/propose_requirements_update.sh
- link-logs
publishers:
- console-log