Hi Anita,
Thanks for the clarification. I will plan on attending the summit session
on this topic (proposed by Kurt, I believe).
I have to admit that I have to always keep an eye out to ensure nothing is
broken in our CI because of any upgrade of packages, etc. and act
accordingly. If new unified
Hi Ramy,
Take me in account. I'm interested in a common solution and I'm trying to
get more involved in the community, so I think that could be a nice
initiative to contribute to the community. If I can help, would be awesome.
I'll start to attend to third party ci meetings.
Regards
On Fri,
)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators:
Let's use a common CI Solution!
Hello Ramy
Take me in account ☺
We used puppet modules located in system-config to install zuul and nodepool.
Also there were a lot manual configuration.
Maybe someday
On 04/20/2015 04:39 PM, Sukhdev Kapur wrote:
Hi Ramy,
While I agree, in principal, with this line of thinking and goal, my
concern will be how much extra work is it going to create for existing CI
owners?
Our Ci system has been stable for a long time, and we put in a good amount
of effort
on
recreating/maintaining the ‘common’ portions of 3rd party ci.
Ramy
From: Sukhdev Kapur [mailto:sukhdevka...@gmail.com]
Sent: Monday, April 20, 2015 1:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI
, April 20, 2015 8:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's
use a common CI Solution!
All Third-Party CI operators:
We’ve got 85 Third Party CI systems registered in the wiki[1], all of them
Hi Ramy,
While I agree, in principal, with this line of thinking and goal, my
concern will be how much extra work is it going to create for existing CI
owners?
Our Ci system has been stable for a long time, and we put in a good amount
of effort to get it to that point. Our CI is not based upon
You rock, Ramy. Seriously, awesome work.
-jay
On 04/20/2015 01:17 AM, Asselin, Ramy wrote:
All Third-Party CI operators:
We’ve got 85 Third Party CI systems registered in the wiki[1], all of
them running a variety of closed open-source solutions.
Instead of individually maintaining all
On 04/20/2015 03:19 AM, Jaume Devesa wrote:
Hi Ramy,
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!
I do hope luqas
Hi Ramy,
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
Thanks Ramy!
I'd suggest that we use the cross-project session I proposed [1] for
Liberty summit as a working session primarily focused on this work [2].
[1]
https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing
[2]
All Third-Party CI operators:
We’ve got 85 Third Party CI systems registered in the wiki[1], 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
12 matches
Mail list logo
