[openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!
devvesa at gmail.com
Mon Apr 20 07:19:52 UTC 2015
Soon I'll be the responsible of the Midokura's third-party CI, which has been
mute for a while because a flaky physical resources that our sys admins
couldn't take care because they are overloaded of work...
Count on me!
On Mon, 20 Apr 2015 05:17, Asselin, Ramy wrote:
> All Third-Party CI operators:
> We’ve got 85 Third Party CI systems registered in the wiki, all of them running a variety of closed & open-source solutions.
> Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution.
> If that sounds good to you, there’s an Infra-spec that’s been approved  to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us.
> We’ve got stories defined , and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” .
> For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/
> If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings .
>  https://wiki.openstack.org/wiki/ThirdPartySystems
>  http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
>  https://storyboard.openstack.org/#!/story/2000101
>  https://review.openstack.org/#/q/topic:downstream-puppet,n,z
>  https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Software Engineer at Midokura
More information about the OpenStack-dev