About the constraints url.

Doug Hellmann doug at doughellmann.com
Mon May 27 23:26:11 UTC 2019

> On May 27, 2019, at 6:48 PM, Tony Breeds <tony at bakeyournoodle.com> wrote:
> On Mon, May 27, 2019 at 02:48:14PM +0100, Sean Mooney wrote:
>>> The wording there is admittedly confusing: these URLs aren't "wrong",
>>> per se, they're just not what we're aiming for going forward.
>>> You
>>> probably want to look at this email:
>>> http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006478.html
>>> The reason for the -1s is presumably so we can do things correctly now
>>> rather than having to fix them again in the future.
>> why would we prefer the release repo over git?
> There are a couple of reasons.
> 1. Using release.o.o allows us is maintain the project state in one
> location therefore removing a race around branch time.   When pointing
> directly at git the constraints file for $branch doesn't exist until the
> requirements repo branches.  So if $project merges an update to tox.ini
> pointing that the constraints file for $branch that project on the new
> stable branch is running without constraints .... Hmm actually this in
> more nuanced that I have previously understood as I think we might
> actually be safe in the gate .... I'll look into that.

The gate always uses a local copy of the constraints list. The race condition is on developers’ local systems, where the old style URL will point to something that does not exist until the requirements repo is branched. 


More information about the openstack-discuss mailing list