)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"f04c066691fda5a8d06561511684382e676cecee","unresolved":false,"context_lines":[{"line_number":9,"context_line":"This adds a -bindep option to the key development library install"},{"line_number":10,"context_line":"functions.  With this option the bindep.txt file will be referenced"},{"line_number":11,"context_line":"and the relevant packages installed."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: I856f1f59fca49b6020920d8f859b797f3b904300"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":9,"id":"bfdaf3ff_873bb136","line":12,"updated":"2019-01-14 06:01:25.000000000","message":"This has been tested in \n\n https://review.openstack.org/#/c/626068/\n\nin the nodepool-functional-py35-src job (logs at [1])\n\nA caveat is that it is not particularly useful for projects that mix jobs doing source installation with released installation (for example, nodepool runs a regular job and a -src job) because we have no bindep installation when installing from upstream pypi.  So in that case, you still need the rpm/deb files anyway.\n\nI don\u0027t really see any option but making it opt-in.  Various project\u0027s bindep sources are in various states of usefulness and automatically trying to install could cause all sorts of problems; and an additional complication is that they will have to specify particular profiles for the testing environment.\n\n[1] http://logs.openstack.org/68/626068/4/check/nodepool-functional-py35-src/6fe2280/","commit_id":"58243f6203f3385039fe7124b037d5abf7e1d59e"}]}
