Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-07-17 Thread Nikhil Manchanda
Anita Kuno writes: > [...] > Nik and I have talked. Since J2 is too far away to let a system run > without recheck capability (as Joe points out, this is not in compliance > with third party ci requirements), Nik is currently following up on > Sukdev's wiki page (if someone can help Sukdev learn

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Joe Gordon
On Jun 29, 2014 8:53 PM, "Anita Kuno" wrote: > > On 06/29/2014 08:38 PM, Nikhil Manchanda wrote: > >> As per http://ci.openstack.org/third_party.html#requirements this is not > > an acceptable short term solution. > > > > Which is one of the major reasons why we're planning on killing the whole >

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Anita Kuno
On 06/29/2014 08:38 PM, Nikhil Manchanda wrote: >> As per http://ci.openstack.org/third_party.html#requirements this is not > an acceptable short term solution. > > Which is one of the major reasons why we're planning on killing the whole > third-party rdjenkins > tests, and moving all of our trov

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Nikhil Manchanda
> As per http://ci.openstack.org/third_party.html#requirements this is not an acceptable short term solution. Which is one of the major reasons why we're planning on killing the whole third-party rdjenkins tests, and moving all of our trove testing to OpenStack infra. At this point, I'd really li

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Joe Gordon
On Jun 29, 2014 7:09 PM, "Nikhil Manchanda" wrote: > > Long term, we're looking to move away from running the integration tests in the third > party reddwarf-jenkins, so this should soon go away. > > FWIW, in the short term, the re-trigger permissions are based on the trove-developers > group in L

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Nikhil Manchanda
Long term, we're looking to move away from running the integration tests in the third party reddwarf-jenkins, so this should soon go away. FWIW, in the short term, the re-trigger permissions are based on the trove-developers group in LaunchPad (https://launchpad.net/~trove). Matt, I've added you a

Re: [openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Denis Makogon
Hello, Mat. You need to log into https://rdjenkins.dyndns.org/job/Trove-Gate/ (Auth system uses Launchpad OpenID). Then you need to find certaun job you need to click "Retrigger". The End. FYI i already retrigged your job. You're welcome. Best regards, Denis Makogon On Sun, Jun 29, 2014 at 4

[openstack-dev] [trove] how to trigger a recheck of reddwarf CI?

2014-06-29 Thread Matt Riedemann
The reddwarf 3rd party CI is failing on an oslo sync patch [1] but Jenkins is fine, I'm unable to find any wiki or guideline on how to recheck just the reddwarf CI, is that possible? [1] https://review.openstack.org/#/c/103232/ -- Thanks, Matt Riedemann _