Open Stack

On Mon, Jun 30, 2014 at 3:19 AM, Luke Gorrie <luke at tail-f.com> wrote:
> Howdy!
>
> Paging other 3rd party CI operators...
>
> I would like to run a simple and robust 3rd party CI. Simple as in a small
> number of moving parts, robust as in unlikely to make mistakes due to
> unexpected problems.
>
> I'm imagining:
>
> - 100 lines of shell for the implementation.
>
> - Minimum of daemons. (Just Jenkins? Ideally not even that...)
>
> - Robust detection of operational problems (CI bugs) vs system-under-test
> problems (changes that should be voted against).
>
> - Effective notifications on all errors or negative votes.
>
> Does anybody already have an implementation like this that they would like
> to share? (Is anybody else wanting something in this direction?)
>
> I've been iterating on 3rd party CI mechanisms (currently onto my 3rd
> from-scratch setup) and I have not been completely satisfied with any of
> them. I would love to hear from someone who has a minimalist implementation
> that they are happy with :).
>
> Cheers,
> -Luke
>
It would be great to get you to join the 3rd Party meeting [1] in
#openstack-meeting at 1800UTC to discuss this. Can you make it today
Luke?

Thanks!
Kyle

[1] https://wiki.openstack.org/wiki/Meetings/ThirdParty
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>