On Thu, Aug 17, 2017 at 04:47:14PM -0500, Matthew Thode wrote:
> Hi all,
>
> It's time to unfreeze the requirements repo.
>
> For projects that have branched (most everyone at this point) this
> won't be a change.
>
> For projects that have yet to branch, you will need to look out for
> and block global requirements bot updates until you've branched.
> You will also need to look out for test failures in your gating as you
> mau be pulling in master (queens) upper-constraints instead of pike.
> The workaround for this is to change your tox.ini temporarilly to target
> the pike branch for fetching the upper-constraints.txt file. It'd be
> better to just branch if you can though.
That won't work. As the gate doesn't use that URL is copy's the file
from the requirements repo from the same branch into the projects
workspace. See the various run-*.sh scripts like:
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/run-tox.sh#n119
So if a constraints update on master breaks your prep for pike please
reach out quickly to the requirements team.
Yours Tony.
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
