[OpenStack-Infra] [third-party] Third Party CI Dashboard

2014-11-17 Thread Steve Weston
Greetings, As was discussed in the Third-Party meeting today[1], I have created the spec for the Third Party CI Dashboard[2]. As you'll see in the spec, I have created a test server instance to demonstrate the Dashboard[3]. Everyone who is interested, please check it out and provide your fe

[OpenStack-Infra] Naming for project-specific external test accounts

2014-11-17 Thread Jeremy Stanley
When we put together our third-party CI account naming scheme a few months ago, discussion was mostly focused on how to avoid confusion on official projects where we have upwards of 50 systems providing feedback on a proposed change. Requirements like "include the name of your company and subsystem

Re: [OpenStack-Infra] Hyper-V CI missing logs

2014-11-17 Thread Octavian Ciuhandu
Hi Anita, The “check hyper-v” reference in the CI comments is already included since we first implemented it, for any build failure. The current message is: “Build failed. For rechecking only on the Hyper-V CI, add a review comment with check hyper-v" Thank you, Octavian. > On 17 Nov 2014,

Re: [OpenStack-Infra] Hyper-V CI missing logs

2014-11-17 Thread Anita Kuno
On 11/17/2014 03:02 PM, Octavian Ciuhandu wrote: > Hi all, > > We have experienced a severe hardware failure and the storage for the logs of > the CI runs was also being affected. We have recovered all that could be > saved on the new dedicated server. > > If you find any patchset that has the

[OpenStack-Infra] Hyper-V CI missing logs

2014-11-17 Thread Octavian Ciuhandu
Hi all, We have experienced a severe hardware failure and the storage for the logs of the CI runs was also being affected. We have recovered all that could be saved on the new dedicated server. If you find any patchset that has the logs missing, please issue a “check hyper-v” command to gener

Re: [OpenStack-Infra] Chicken and Egg patches

2014-11-17 Thread Monty Taylor
I'm on my phone and will follow up when I am not. Tl;Dr,they have a valid use case we don't have upstream that bears thought On Nov 17, 2014 3:11 PM, Clint Byrum wrote: > > Excerpts from Spencer Krum's message of 2014-11-17 02:36:20 -0800: > > Hi, > > > > I help run a clone of infra and our d

Re: [OpenStack-Infra] Chicken and Egg patches

2014-11-17 Thread Clint Byrum
Excerpts from Spencer Krum's message of 2014-11-17 02:36:20 -0800: > Hi, > > I help run a clone of infra and our developers have a desire to land > 'chicken and egg' patches. What I mean by this is one patchset on one > project and another patchset on another project such that tests cannot pass >

Re: [OpenStack-Infra] Chicken and Egg patches

2014-11-17 Thread Monty Taylor
Hi! We do not land such patches. We make sure that there is a sequence in which they can land. We have actually come to realize that this is a feature not a bug, as it is important for people doing CD. Monty On Nov 17, 2014 7:36 AM, Spencer Krum wrote: > > Hi, > > I help run a clone of infra

[OpenStack-Infra] Chicken and Egg patches

2014-11-17 Thread Spencer Krum
Hi, I help run a clone of infra and our developers have a desire to land 'chicken and egg' patches. What I mean by this is one patchset on one project and another patchset on another project such that tests cannot pass on either individually, but together, everything works. Right now we can't land