[openstack-dev] [all] periodic jobs for master

Ihar Hrachyshka ihrachys at redhat.com
Wed Oct 29 16:36:25 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 25/10/14 00:16, James E. Blair wrote:
> Andrea Frittoli <andrea.frittoli at gmail.com> writes:
> 
>> I also believe we can find ways to make post-merge / periodic
>> checks useful. We need to do that to keep the gate to a sane
>> scale.
> 
> Yes, we have a plan to do that that we outlined at the infra/QA
> meetup this summer and described to this list in this email:
> 
> http://lists.openstack.org/pipermail/openstack-dev/2014-July/041057.html
>
>  Particularly this part, but please read the whole message if you
> have not already, or have forgotten it:
> 
> * For all non gold standard configurations, we'll dedicate a part
> of our infrastructure to running them in a continuous background
> loop, as well as making these configs available as experimental
> jobs. The idea here is that we'll actually be able to provide more 
> configurations that are operating in a more traditional CI (post 
> merge) context. People that are interested in keeping these bits 
> functional can monitor those jobs and help with fixes when needed. 
> The experimental jobs mean that if developers are concerned about 
> the effect of a particular change on one of these configs, it's
> easy to request a pre-merge test run.  In the near term we might
> imagine this would allow for things like ceph, mongodb, docker, and
> possibly very new libvirt to be validated in some way upstream.
> 
> * Provide some kind of easy to view dashboards of these jobs, as
> well as a policy that if some job is failing for > some period of
> time, it's removed from the system. We want to provide whatever
> feedback we can to engaged parties, but people do need to realize
> that engagement is key. The biggest part of putting tests into
> OpenStack isn't landing the tests, but dealing with their
> failures.
> 
> I'm glad to see people interested in this.  If you're ready to 
> contribute to it, please stop by #openstack-infra or join our next
> team meeting[1] to discuss how you can help.

I'm sorry I've missed the email that you referred to before. Indeed,
it looks like I'm not the first one who started to think about the
matter. Summit wise, will there be any sessions where the subject will
be discussed?

> 
> -Jim
> 
> [1] https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting
> 
> _______________________________________________ OpenStack-dev
> mailing list OpenStack-dev at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQEcBAEBCgAGBQJUUReJAAoJEC5aWaUY1u57H6QH/17FbSgU5vvwM03OzfSCpsZi
IAG6T/UThfVQ8H08cHk6R+US9TkKdrl1QTJCDr70QhKbzLy+7OKp/H3B/PIuhaaN
enqDp7ku3XQotxRTw6AW/ksLb9LCZCMMRtDiFOemC2TI6jqNXBKRz+TwFh2terY3
a9YH8IoYk2qYyLZ0fcv+OXdS7If+zD3u0PGOAJCBwKWbpUv82STdzjbDCATM779g
rBC9BgYheSYPYfNjxpPKb/UN7aJZ/4TRPgK6MWktHGmqhZzZmlFPme+7x0rLdMvz
5/4m2Oh6k6Th/y1TV65jYcZID50w1esMO7tGdvmtX6Drc9lB9Y0r3fQF7R2eYpE=
=FmKW
-----END PGP SIGNATURE-----



More information about the OpenStack-dev mailing list