Explicitly clone requirements for bifrost

Bifrost expects to be able to have a complete folder on
disk for accessing the upper-constraint data, as opposed
to the single file on disk. Retooling to capture/use the
the single file will create more alternate paths that must
be taken to perform the install and it seems less ideal
in a deployed environment where the git repository in whole
provides some confidence of and history of the file.

Since we don't explicitly clone our own copy in OpenStack CI
we will have zuul cloner grab a copy for us.

Change-Id: I64d1744c776c20d906a29e072602c1909853da25
This commit is contained in:
Julia Kreger 2017-05-25 15:02:45 +00:00
parent 8f2a6c9fbf
commit 56b50a2241
1 changed files with 6 additions and 3 deletions

View File

@ -22,7 +22,8 @@
openstack/python-ironicclient \
openstack-infra/shade \
openstack/ironic-inspector \
openstack/python-ironic-inspector-client
openstack/python-ironic-inspector-client \
openstack/requirements
export GIT_BASE=$(pwd)
export UPPER_CONSTRAINTS_FILE=$WORKSPACE/upper-constraints.txt
cd openstack/bifrost
@ -57,7 +58,8 @@
openstack/python-ironicclient \
openstack-infra/shade \
openstack/ironic-inspector \
openstack/python-ironic-inspector-client
openstack/python-ironic-inspector-client \
openstack/requirements
export GIT_BASE=$(pwd)
export UPPER_CONSTRAINTS_FILE=$WORKSPACE/upper-constraints.txt
cd openstack/bifrost
@ -92,7 +94,8 @@
openstack/python-ironicclient \
openstack-infra/shade \
openstack/ironic-inspector \
openstack/python-ironic-inspector-client
openstack/python-ironic-inspector-client \
openstack/requirements
export GIT_BASE=$(pwd)
export UPPER_CONSTRAINTS_FILE=$WORKSPACE/upper-constraints.txt
cd openstack/bifrost