Mark all files that are run (and not only sourced) as executable.
Remove files bump-milestone.sh, run-xmllint.sh and wait_for_nova.sh,
those are not used anywhere in OpenStack (according to codesearch.o.o
and local git grep).
Change-Id: Ie344c9f9f8cc39b102f0147ecffa189e1b83da1e
In trying to add constraints support to os-api-ref we hit a case where
installing os-api-ref with this script will also update requirements.
If a requirement isn't blocked in thw gate *or* os-api-ref hasn't merged the
proposal-bit's update this can lead to failures.
This change addresses that by installing openstack-requirements and
removing os-api-ref from upper-constraints.txt. Then when it installs
os-api-ref the version from git is appropriate BUT all requirements are
also constrained.
Note: This assumes running in the gate and that the git setup has copied
the upper-constraints.txt into a local file and set the
UPPER_CONSTRAINTS_FILE appropriately. The new commands will fail and
cause job failures if these pre-conditions are not met.
Change-Id: Ic9b49dbd2b9b8c991fa6d21545460ce015bcc320
Needed-By: I7ad1c2afda29b095ff3d53db5eec7101f8816c2e
The -e install during testing apparently will not actually replace an
existing os-api-ref with the development one (as experienced with lots
of local testing). Switching to just -U gives the desired results.
Change-Id: I7740c8f6219327bb00646a086afe114a5151b7d5
I think that because the cloned path is the same name as the upstream
module, pip is installing the upstream module not the cloned path. Fix
how we pip install os-api-ref to make this work.
Remove the -q until this is working, to help with debugging, we can
set -q again when we know it all works.
Change-Id: I4fb65bd7a47c61d9d91c0064a8d6852ca5326163
This allows using the zuul api-ref reference on a project in question,
it will let us see what api-ref changes look like on existing api-ref
source trees.
Change-Id: I263278370d93cd4998ee3da518a5b0de6bd80548