[openstack-dev] [cinder] 3rd party ci names for use by official cinder mandated tests

Anita Kuno anteaya at anteaya.info
Wed Jul 2 15:00:45 UTC 2014

On 07/01/2014 01:13 PM, Asselin, Ramy wrote:
> 3rd party ci names is currently becoming a bit controversial for what we're trying to do in cinder: https://review.openstack.org/#/c/101013/
> The motivation for the above change is to aid developers understand what the 3rd party ci systems are testing in order to avoid confusion.
> The goal is to aid developers reviewing cinder changes to understand which 3rd party ci systems are running official cinder-mandated tests and which are running unofficial/proprietary tests.
> Since the use of "cinder" is proposed to be "reserved" (per change under review above), I'd like to propose the following for Cinder third-party names under the following conditions:
> {Company-Name}-cinder-ci
> *         This CI account name is to be used strictly for official cinder-defined dsvm-full-{driver} tests.
> *         No additional tests allowed on this account.
> o    A different account name will be used for unofficial / proprietary tests.
> *         Account will only post reviews to cinder patches.
> o    A different account name will be used to post reviews in all other projects.
> *         Format of comments will be (as jgriffith commented in that review):
> {company name}-cinder-ci
>    dsvm-full-{driver-name}                           pass/fail
>    dsvm-full-{other-driver-name}                 pass/fail
>    dsvm-full-{yet-another-driver-name}       pass/fail
> Thoughts?
> Ramy
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks for starting this thread, Ramy.

I too would like Cinder third party ci systems (and systems that might
test Cinder now or in the future) to weigh in and share their thoughts.

We do need to agree on a naming policy and whatever that policy is will
frame future discussions with new accounts (and existing ones) so let's
get some thoughts offered here so we all can live with the outcome.

Thanks again, Ramy, I appreciate your help on this as we work toward a

Thank you,

More information about the OpenStack-dev mailing list