I believe the previous CI ran on the Openstack CI infrastructure, but was constantly broken and unmaintained (I'm working from memory here). The Cinder team have never cared /where/ the CI is run, and if infra is happy to host the Gluster CI jobs then great. What is needed is somebody to maintain them long term, which I believe is what was missing, causing the removal.
On 26 July 2017 at 13:30, Jeremy Stanley <[email protected]> wrote: > On 2017-07-26 12:56:55 +0200 (+0200), Niels de Vos wrote: > [...] >> My current guess is that adding a 3rd party CI [3] for Gluster is >> the only missing piece? > [...] > > I thought GlusterFS was free/libre software. If so, won't the Cinder > team allow upstream testing in OpenStack's CI system for free > backends/drivers? Maintaining a third-party CI system for that seems > like overkill, but I'm unfamiliar with Cinder's particular driver > testing policies. > -- > Jeremy Stanley > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Duncan Thomas __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
