On 13 April 2015 at 13:09, Robert Collins <robe...@robertcollins.net> wrote: > On 13 April 2015 at 12:53, Monty Taylor <mord...@inaugust.com> wrote: > >> What we have in the gate is the thing that produces the artifacts that >> someone installing using the pip tool would get. Shipping anything with >> those artifacts other that a direct communication of what we tested is >> just mean to our end users. > > Actually its not. > > What we test is point in time. At 2:45 UTC on Monday installing this > git ref of nova worked. > > Noone can reconstruct that today. > > I entirely agree with the sentiment you're expressing, but we're not > delivering that sentiment today.
This observation led to yet more IRC discussion and eventually https://etherpad.openstack.org/p/stable-omg-deps In short, the proposal is that we: - stop trying to use install_requires to reproduce exactly what works, and instead use it to communicate known constraints (> X, Y is broken etc). - use a requirements.txt file we create *during* CI to capture exactly what worked, and also capture the dpkg and rpm versions of packages that were present when it worked, and so on. So we'll build a git tree where its history is an audit trail of exactly what worked for everything that passed CI, formatted to make it really really easy for other people to consume. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ 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
