[openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?
clint at fewbar.com
Thu Jan 8 18:38:09 UTC 2015
Excerpts from Chris Jones's message of 2015-01-08 10:16:14 -0800:
> > On 8 Jan 2015, at 17:58, Clint Byrum <clint at fewbar.com> wrote:
> > Excerpts from Steven Hardy's message of 2015-01-08 09:37:55 -0800:
> > So you can probably setup a devpi instance locally, and upload the
> > commits you want to it, and then build the image with the 'pypi' element
> Given that we have a pretty good release frequency of all our tools, is this burden on devs/testers actually justified at this point, versus the potential consistency we could have with source repo flexibility in other openstack components?
We've been discussing in #tripleo and I think you're right. I think we
can solve this by just switching to source-repositories and providing
a relatively simple tool to set release tags when people want released
More information about the OpenStack-dev