On 2015-05-29 10:37:43 +0100 (+0100), Derek Higgins wrote: [...] > I think the feature in delorean that is most useful is that it > will continue to maintain a history of usable package repositories > representing the openstack projects over time, for this we would > need a long running instance, but that can happen outside of > infra. [...]
It could potentially even happen in our infrastructure, as long as the package builds happen on different machines from the servers serving the results of those builds. We don't eschew all long-running hosts, just long-running job workers. However, whether OpenStack's project infrastructure wants to be responsible for serving package download repositories for things it doesn't use is a separate discussion entirely. To me, the main benefits are that you have somewhere to collaborate on packaging work with a code review system, and our CI can further assist you in that effort by providing feedback on whether or not a proposed packaging change is able to successfully build a package (and perhaps even whether that package can be installed and exercised in some arbitrary way). -- Jeremy Stanley __________________________________________________________________________ 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
