What is the criteria for this? The OpenDaylight Jenkins has been
reliably voting for a few weeks now, I'm wondering how and when we can
get it's voting rights approved.
Thanks!
Kyle
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 03/31/2014 06:02 PM, Kyle Mestery wrote:
What is the criteria for this? The OpenDaylight Jenkins has been
reliably voting for a few weeks now, I'm wondering how and when we can
get it's voting rights approved.
Thanks!
Kyle
___
OpenStack-dev
Fellow developers,
I just put together a wiki describing the Arista Third Party Setup.
In the attached document we provide a link to the modified Gerrit Plugin to
handle the regex matching for the Comment Added event so that
recheck/reverify no bug/ can be handled.
Have a question regarding the Jenkins/Gerrit setup for third party testing
setups.
When Jenkins get triggered by a patchset through the Gerrit trigger
plug-in, you can execute a set of shell scripts. How do you get the
information about the patchset that triggered the test? In particular, in
questions)
Subject: [openstack-dev] [neutron] [third-party-testing] Which patchset
triggered the test
Have a question regarding the Jenkins/Gerrit setup for third party testing
setups.
When Jenkins get triggered by a patchset through the Gerrit trigger plug-in,
you can execute a set of shell
On Mon, 2014-01-20 at 14:26 -0500, Mohammad Banikazemi wrote:
Have a question regarding the Jenkins/Gerrit setup for third party
testing setups.
When Jenkins get triggered by a patchset through the Gerrit trigger
plug-in, you can execute a set of shell scripts. How do you get the
/2014 04:25 PM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Which
patchset triggered the test
Mohammad,
You can get the information you want from the environment variables that
the Gerrit plugin sets.
Just like it was mentioned here:
https
On Thu, 2014-01-16 at 15:37 +, Sullivan, Jon Paul wrote:
From: Jay Pipes [mailto:jaypi...@gmail.com]
On Thu, 2014-01-16 at 10:39 +, Sullivan, Jon Paul wrote:
From: Kyle Mestery [mailto:mest...@siliconloons.com]
FYI, here [1] are the meeting logs from today’s meeting.
Jay Pipes jaypi...@gmail.com wrote on 01/17/2014 04:32:55 PM:
From: Jay Pipes jaypi...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 01/17/2014 04:37 PM
Subject: Re: [openstack-dev] [neutron] [third-party-testing
-Original Message-
From: Kyle Mestery [mailto:mest...@siliconloons.com]
Sent: 15 January 2014 22:53
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing
information
FYI, here [1] are the meeting logs
From: Mohammad Banikazemi [mailto:m...@us.ibm.com]
Sullivan, Jon Paul jonpaul.sulli...@hp.commailto:jonpaul.sulli...@hp.com
wrote on 01/16/2014 05:39:04 AM:
I can't recommend Jenkins Job Builder highly enough if you use Jenkins.
[2] https://github.com/openstack-infra/jenkins-job-builder
From: Jay Pipes [mailto:jaypi...@gmail.com]
On Thu, 2014-01-16 at 10:39 +, Sullivan, Jon Paul wrote:
From: Kyle Mestery [mailto:mest...@siliconloons.com]
FYI, here [1] are the meeting logs from today’s meeting.
A couple of things have become apparent here:
1. No one
Apologies for an almost duplicate post, I corrected the mistake in the example.
Ooops.
-Original Message-
From: Sullivan, Jon Paul
Sent: 16 January 2014 15:38
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [third-party
do the meeting today.
From:Kyle Mestery mest...@siliconloons.com
To:OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting
Thursday. We'll still do the meeting today.
From:Kyle Mestery mest...@siliconloons.com
To:OpenStack Development Mailing List \(not for usage
questions\) openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing
---Apologies folks, I
meant 2200 UTC Thursday. We'll still do the meeting today.
From:Kyle Mestery mest...@siliconloons.com
To:OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron
\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today.
On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com
UTC Thursday. We'll still do the meeting today.
From: Kyle Mestery mest...@siliconloons.com
To: OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date: 12/19/2013 09:17 AM
Subject: Re: [openstack-dev] [neutron] [third-party-testing
:Kyle Mestery mest...@siliconloons.com
To:OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting tomorrow
Apologies folks, I
: [openstack-dev] [neutron] [third-party-testing] Sharing
information
Thanks for sending this note Mohammad. I am all in favor of another
3rd party testing meeting on IRC. How about if we shoot for tomorrow,
Wednesday the 15, at 2200 UTC? Please ack if that works for everyone.
Thanks,
Kyle
...@siliconloons.com
To:OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing]
Reminder:Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday
/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing]
Reminder:Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today.
On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote:
Wouldn't 2200 UTC be in about
Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today
@lists.openstack.org,
Date:12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today.
On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote:
Wouldn't 2200 UTC
questions
\) openstack-dev@lists.openstack.org,
Date: 12/19/2013 09:17 AM
Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:
Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today.
On Dec 18, 2013, at 4:40 PM
Hi,
We are developing a neutron plugin that works with our network controller.
Do we need to have 2 sets of tests for the plugin
i) tests that can be run against the network controller in our third party
test setup (to vote on changes to the plugin)
ii) tests that can be run in the OpenStack test
Apologies folks, I meant 2200 UTC Thursday. We'll still do the
meeting today.
On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote:
Wouldn't 2200 UTC be in about 20 mins?
On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote:
Hi,
It seems the meeting was not held
Hi,
I'm sorry I could not make it to meeting.
However, I can see clearly see the progress being made from gerrit!
One thing which might be worth mentioning is that some of the new jobs are
already voting.
However, in some cases the logs are either not accessible, and in other
cases the job seem
: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting
tomorrow
Hi,
I'm sorry I could not make it to meeting.
However, I can see clearly see the progress being made from gerrit!
One thing which might be worth mentioning is that some of the new jobs are
already voting.
However, in some
Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt.
We'll be looking at this etherpad [1] again, and continuing discussions from
last week.
Thanks!
Kyle
[1] https://etherpad.openstack.org/p/multi-node-neutron-tempest
___
Hi,
It seems the meeting was not held on 2200 UTC on Wednesday (today).
Do you mean 2200 UTC on Thursday ?
Thanks.
On Thu, 12 Dec 2013 11:43:03 -0600
Kyle Mestery mest...@siliconloons.com wrote:
Hi everyone:
We had a meeting around Neutron Third-Party testing today on IRC.
The logs are
Wouldn't 2200 UTC be in about 20 mins?
On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote:
Hi,
It seems the meeting was not held on 2200 UTC on Wednesday (today).
Do you mean 2200 UTC on Thursday ?
Thanks.
On Thu, 12 Dec 2013 11:43:03 -0600
Kyle Mestery
Hi everyone:
We had a meeting around Neutron Third-Party testing today on IRC.
The logs are available here [1]. We plan to host another meeting
next week, and it will be at 2200 UTC on Wednesday in the
#openstack-meeting-alt channel on IRC. Please attend and update
the etherpad [2] with any items
Hi Yoshihiro,
In my opinion the use of filters on changes is allowed by the smoketesting
policy we defined.
Notwithstanding that the approach of testing every patch is definitely the
safest, I understand in some cases the volume of patchsets uploaded to
gerrit might overwhelm the plugin-specific
Hi Salvatore,
Thank you for your reply.
2013/12/11 Salvatore Orlando sorla...@nicira.com:
Hi Yoshihiro,
In my opinion the use of filters on changes is allowed by the smoketesting
policy we defined.
Notwithstanding that the approach of testing every patch is definitely the
safest, I
On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote:
Hi Neutron team,
I'm working on building Third-party testing for Neutron Ryu plugin.
I intend to use Jenkins and gerrit-trigger plugin.
It is required that Third-party testing provides verify vote for
all changes to a
2013/12/10 Matt Riedemann mrie...@linux.vnet.ibm.com:
On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote:
Hi Neutron team,
I'm working on building Third-party testing for Neutron Ryu plugin.
I intend to use Jenkins and gerrit-trigger plugin.
It is required that Third-party
37 matches
Mail list logo
