Re: [OpenStack-Infra] Request for Upstream Service Account
Due to the new account name rules, I've changed your account info: short username: hds-ci long username: "HDS CI" Account will be ready in 5 mins. On Wed, Jul 23, 2014 at 8:24 PM, Steven Sonnenberg wrote: > Email: openstackdevelopm...@hds.com > Account Username (short): hds-review > Account Username (long): HDS OpenStack CI > Contact Info: Steven Sonnenberg, steve.sonnenb...@hds.com, IRC handle: > steveisoft, Mobile: 443-929-6543 > Public Key: sh-rsa > B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBMovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc= > openstackdevelopm...@hds.com > > > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] 3rd Party CI Service Account Request
full name: "Dell StorageCenter CI" id: dell-storagecenter-ci Account will be ready in 5 mins. On Wed, Jul 23, 2014 at 8:59 PM, Anita Kuno wrote: > On 07/23/2014 12:46 PM, Sean McGinnis wrote: >> Sorry, didn't mean to seem impatient. Just want to make sure I didn't miss >> anything that would cause the process to be held up on me. >> >> Thanks for your help with this! >> > Yep, no problem. > >> -Original Message- >> From: Anita Kuno [mailto:ante...@anteaya.info] >> Sent: Wednesday, July 23, 2014 11:43 AM >> To: openstack-infra@lists.openstack.org >> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request >> >> On 07/22/2014 03:17 PM, Sean McGinnis wrote: >>> Hello Anita, >>> >>> Any luck on getting a service account created? Or do you need any more >>> information to help on the naming? Just let me know. >>> >>> Thanks, >>> Sean >>> >> Well Gerrit changes to allow me to have permissions to create and edit >> accounts just got merged upstream, so hopefully I should be able to help >> you soon. >> >> Be patient, Sergey might get to your account request first. >> >> Thanks Sean, >> Anita. >> > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Third Party CI System account
Hi Wilfredo, as Anita said, please, provide info about your plans for ci account usage. Thanks. On Fri, Jul 25, 2014 at 12:45 AM, Anita Kuno wrote: > On 07/22/2014 05:15 PM, Wilfredo Ronsini wrote: >> I work in the Flextronics Institute of Technology and I am in the process of >> setting an OpenStack CI server. >> >> Please, create a Gerrit user account. >> >> Preferred username: wronsini >> >> Best regards, >> Wilfredo Raphael Ronsini Junior >> email: wilfredo...@fit-tecnologia.org.br >> >> Legal Disclaimer: >> The information contained in this message may be privileged and >> confidential. It is intended to be read only by the individual or entity to >> whom it is addressed or by their designee. If the reader of this message is >> not the intended recipient, you are on notice that any distribution of this >> message, in any form, is strictly prohibited. If you have received this >> message in error, please immediately notify the sender and delete or destroy >> any copy of this message! >> >> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > Hi Wilfredo: > > The need for a third party ci account from gerrit comes into play if you > are looking to comment on patches with some kind of verification. > > What do you plan on verifying? > > For instance businesses often want to verify their proprietary code or > hardware will work with each evaluated patch. What might you be verifying? > > If you aren't going to be reporting back any verification status, you > can hook into gerrit events with a normal user account using: > ssh -p 29418 @review.openstack.org gerrit stream-events > > and you can have your system trigger off of gerrit events and you don't > need to report anything back to the patch you are using as a trigger. > > Thanks Wilfredo, > Anita. > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request for Upstream Service Account
I've responded to the initial email. Please, note that I've changed a bit account short and full names. On Tue, Jul 29, 2014 at 8:29 PM, Steven Sonnenberg wrote: > Hi team, > We had an issue with the mail server settings rejecting non-authenticated > email senders. > Please re-send any information provided for the service account. > -steve > > Email: openstackdevelopm...@hds.com > Account Username (short): hds-review > Account Username (long): HDS OpenStack CI > Contact Info: Steven Sonnenberg, steve.sonnenb...@hds.com, IRC handle: > steveisoft, Mobile: 443-929-6543 > Public Key: sh-rsa > B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBMovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc= > openstackdevelopm...@hds.com > > > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] FW: Requesting a Service Account for Third Party CI System
I've changed a bit both short and full usernames: prophetstor-ci and "ProphetStor CI" Account will be ready in 5 mins. On Mon, Aug 4, 2014 at 10:34 AM, Rick Chen wrote: > HI All: > I saw the third-pard CI members still increased, but our account is > not accepted. Can you tell me why? Or how to solve this problem? > Please give me a feedback. > > 1. Attached file. > 2. A preferred username: prophetstor > 3. A human-readable: ProphetStor-CI > 4. Email address: prophetstor...@prophetstor.com > 5. For cinder volume driver certificate. BP: > https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver > >> Please help us to create service account. Thanks. > -Original Message- > From: Rick Chen [mailto:rick.c...@prophetstor.com] > Sent: Monday, July 28, 2014 10:41 PM > To: 'Anita Kuno'; 'openstack-infra@lists.openstack.org' > Cc: 'steve tan'; 'Albert Lin' > Subject: RE: [OpenStack-Infra] Requesting a Service Account for Third Party > CI System > > HI Anita: > Does our service account ready? > I need change below information, please help me to correct? Or tell > me how to change it? >>> 3. A human-readable: Prophetstor-CI --> ProphetStor-CI > > > -Original Message- > From: Anita Kuno [mailto:ante...@anteaya.info] > Sent: Monday, July 28, 2014 3:43 AM > To: Rick Chen; openstack-infra@lists.openstack.org > Cc: 'steve tan'; Albert Lin > Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third Party > CI System > > On 07/27/2014 01:07 PM, Rick Chen wrote: >> Hi Anita: >> Prophetstor is my company name. I plan to verify our cinder volume >> driver. >> BP: >> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver >> Please help us to create service account. Thanks. > Great, thanks Rick. Linking the blueprint really helps. > > We are working on getting me permissions to create accounts, which is soon > but hasn't happened yet. In the meantime one of my infra colleagues may get > the account created before I do. > > Thanks, > Anita. >> >> -Original Message- >> From: Anita Kuno [mailto:ante...@anteaya.info] >> Sent: Saturday, July 26, 2014 9:08 PM >> To: openstack-infra@lists.openstack.org >> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third >> Party CI System >> >> On 07/25/2014 08:36 PM, Rick Chen wrote: >>> Hi Sir: >>> >>> Please help us to create service account, Thanks. >>> >>> >>> >>> 1. Attached file. >>> >>> 2. A preferred username: prophetstor >>> >>> 3. A human-readable: Prophetstor-CI >>> >>> 4. Email address: prophetstor...@prophetstor.com >>> >>> >>> >>> >>> ___ >>> OpenStack-Infra mailing list >>> OpenStack-Infra@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >>> >> Hi Rick: >> >> We are changing our documentation around requesting a service account, >> the patch hasn't been merged yet: >> https://review.openstack.org/#/c/101013/11/doc/source/third_party.rst >> >> So Prophetstor is the name of your company, what details can you give >> me about what you intend to be verifying with your third party ci account? >> It might be a piece of software or hardware or something else. >> The more details you can offer, the better. If you have a blueprint or >> spec for it, linking to the blueprint or spec in your reply is really > helpful. >> >> Thanks Rick, >> Anita. >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] 3rd party CI account request
Anita, could you please confirm that congress-ci "Congress CI" is an acceptable name? On Wed, Jul 30, 2014 at 1:29 AM, Aaron Rosen wrote: > Hi, > > I was on #openstack-infra I should also include a few more things which are > new requirements: > > company: VMware > Providing CI for the Openstack Congress project: > https://github.com/stackforge/congress > > Thanks, > > Aaron > > > On Tue, Jul 29, 2014 at 11:26 AM, Aaron Rosen wrote: >> >> Hi, >> >> I'm following what's outlined here >> (http://ci.openstack.org/third_party.html#requesting-a-service-account) to >> setup a new account for 3rd party testing for a new openstack stackforge >> project. >> >> Desired username: Congress-CI >> contact: congres...@gmail.com >> Pub ssh key attached. >> >> Thanks! >> >> Aaron > > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] FW: Requesting a Service Account for Third Party CI System
Account created. On Mon, Aug 4, 2014 at 2:49 PM, Sergey Lukjanov wrote: > I've changed a bit both short and full usernames: prophetstor-ci and > "ProphetStor CI" > > Account will be ready in 5 mins. > > On Mon, Aug 4, 2014 at 10:34 AM, Rick Chen wrote: >> HI All: >> I saw the third-pard CI members still increased, but our account is >> not accepted. Can you tell me why? Or how to solve this problem? >> Please give me a feedback. >> >> 1. Attached file. >> 2. A preferred username: prophetstor >> 3. A human-readable: ProphetStor-CI >> 4. Email address: prophetstor...@prophetstor.com >> 5. For cinder volume driver certificate. BP: >> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver >> >>> Please help us to create service account. Thanks. >> -Original Message- >> From: Rick Chen [mailto:rick.c...@prophetstor.com] >> Sent: Monday, July 28, 2014 10:41 PM >> To: 'Anita Kuno'; 'openstack-infra@lists.openstack.org' >> Cc: 'steve tan'; 'Albert Lin' >> Subject: RE: [OpenStack-Infra] Requesting a Service Account for Third Party >> CI System >> >> HI Anita: >> Does our service account ready? >> I need change below information, please help me to correct? Or tell >> me how to change it? 3. A human-readable: Prophetstor-CI --> ProphetStor-CI >> >> >> -Original Message- >> From: Anita Kuno [mailto:ante...@anteaya.info] >> Sent: Monday, July 28, 2014 3:43 AM >> To: Rick Chen; openstack-infra@lists.openstack.org >> Cc: 'steve tan'; Albert Lin >> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third Party >> CI System >> >> On 07/27/2014 01:07 PM, Rick Chen wrote: >>> Hi Anita: >>> Prophetstor is my company name. I plan to verify our cinder volume >>> driver. >>> BP: >>> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver >>> Please help us to create service account. Thanks. >> Great, thanks Rick. Linking the blueprint really helps. >> >> We are working on getting me permissions to create accounts, which is soon >> but hasn't happened yet. In the meantime one of my infra colleagues may get >> the account created before I do. >> >> Thanks, >> Anita. >>> >>> -Original Message- >>> From: Anita Kuno [mailto:ante...@anteaya.info] >>> Sent: Saturday, July 26, 2014 9:08 PM >>> To: openstack-infra@lists.openstack.org >>> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third >>> Party CI System >>> >>> On 07/25/2014 08:36 PM, Rick Chen wrote: Hi Sir: Please help us to create service account, Thanks. 1. Attached file. 2. A preferred username: prophetstor 3. A human-readable: Prophetstor-CI 4. Email address: prophetstor...@prophetstor.com ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >>> Hi Rick: >>> >>> We are changing our documentation around requesting a service account, >>> the patch hasn't been merged yet: >>> https://review.openstack.org/#/c/101013/11/doc/source/third_party.rst >>> >>> So Prophetstor is the name of your company, what details can you give >>> me about what you intend to be verifying with your third party ci account? >>> It might be a piece of software or hardware or something else. >>> The more details you can offer, the better. If you have a blueprint or >>> spec for it, linking to the blueprint or spec in your reply is really >> helpful. >>> >>> Thanks Rick, >>> Anita. >>> >>> ___ >>> OpenStack-Infra mailing list >>> OpenStack-Infra@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >>> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > > > > -- > Sincerely yours, > Sergey Lukjanov > Sahara Technical Lead > (OpenStack Data Processing) > Principal Software Engineer > Mirantis Inc. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] 3rd Party CI Service Account Request
Account created. On Mon, Aug 4, 2014 at 2:24 PM, Sergey Lukjanov wrote: > full name: "Dell StorageCenter CI" > id: dell-storagecenter-ci > > Account will be ready in 5 mins. > > On Wed, Jul 23, 2014 at 8:59 PM, Anita Kuno wrote: >> On 07/23/2014 12:46 PM, Sean McGinnis wrote: >>> Sorry, didn't mean to seem impatient. Just want to make sure I didn't miss >>> anything that would cause the process to be held up on me. >>> >>> Thanks for your help with this! >>> >> Yep, no problem. >> >>> -Original Message- >>> From: Anita Kuno [mailto:ante...@anteaya.info] >>> Sent: Wednesday, July 23, 2014 11:43 AM >>> To: openstack-infra@lists.openstack.org >>> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request >>> >>> On 07/22/2014 03:17 PM, Sean McGinnis wrote: Hello Anita, Any luck on getting a service account created? Or do you need any more information to help on the naming? Just let me know. Thanks, Sean >>> Well Gerrit changes to allow me to have permissions to create and edit >>> accounts just got merged upstream, so hopefully I should be able to help >>> you soon. >>> >>> Be patient, Sergey might get to your account request first. >>> >>> Thanks Sean, >>> Anita. >>> >> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > > > -- > Sincerely yours, > Sergey Lukjanov > Sahara Technical Lead > (OpenStack Data Processing) > Principal Software Engineer > Mirantis Inc. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request for Upstream Service Account
Account created. On Mon, Aug 4, 2014 at 2:20 PM, Sergey Lukjanov wrote: > Due to the new account name rules, I've changed your account info: > > short username: hds-ci > long username: "HDS CI" > > Account will be ready in 5 mins. > > On Wed, Jul 23, 2014 at 8:24 PM, Steven Sonnenberg > wrote: >> Email: openstackdevelopm...@hds.com >> Account Username (short): hds-review >> Account Username (long): HDS OpenStack CI >> Contact Info: Steven Sonnenberg, steve.sonnenb...@hds.com, IRC handle: >> steveisoft, Mobile: 443-929-6543 >> Public Key: sh-rsa >> B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBMovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc= >> openstackdevelopm...@hds.com >> >> >> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > > > -- > Sincerely yours, > Sergey Lukjanov > Sahara Technical Lead > (OpenStack Data Processing) > Principal Software Engineer > Mirantis Inc. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Third Party CI System account
On 07/22/2014 05:15 PM, Wilfredo Ronsini wrote: >> I work in the Flextronics Institute of Technology and I am in the process of >> setting an OpenStack CI server. >> >> Please, create a Gerrit user account. >> >> Preferred username: wronsini >> >> Best regards, >> Wilfredo Raphael Ronsini Junior >> email: Wilfredo.Jr at fit-tecnologia.org.br >> >> Legal Disclaimer: >> The information contained in this message may be privileged and >> confidential. It is intended to be read only by the individual or entity to >> whom it is addressed or by their designee. If the reader of this message is >> not the intended recipient, you are on notice that any distribution of this >> message, in any> form, is strictly prohibited. If you have received this >> message in error, please immediately notify the sender and delete or destroy >> any copy of this message! >> >> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> >Hi Wilfredo: > Hi Anita, We need to have our CI system in the list of reviewers of the patches sent to cinder (like, EMC XIO CI, HP Cinder CI, etc). An ordinary gerrit account is enough for that? Thanks, Erlon >The need for a third party ci account from gerrit comes into play if you >are looking to comment on patches with some kind of verification. > > > > >What do you plan on verifying? > >For instance businesses often want to verify their proprietary code or >hardware will work with each evaluated patch. What might you be verifying? > >If you aren't going to be reporting back any verification status, you >can hook into gerrit events with a normal user account using: >ssh -p 29418 @review.openstack.org gerrit stream-events > >and you can have your system trigger off of gerrit events and you don't >need to report anything back to the patch you are using as a trigger. > >Thanks Wilfredo, >Anita. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] How upstream jenkins coohses server
For the CI Test system, I would like to know how to upstream jenkins chooses which Third Party CI will be used, if a ramdom pick or will it choose based on the driver being tested? Is there any customization for the Third Party to test a specific driver? Thanks, Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message! ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] How upstream jenkins coohses server
On 2014-08-04 17:09:31 + (+), Wilfredo Ronsini wrote: > For the CI Test system, I would like to know how to upstream > jenkins chooses which Third Party CI will be used, if a ramdom > pick or will it choose based on the driver being tested? [...] The upstream CI does not choose anything there... each third-party CI system listens to the upstream Gerrit's event stream and reacts to new patchsets and comments. http://ci.openstack.org/third_party.html#reading-the-event-stream Hopefully that helps? -- Jeremy Stanley ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [Infra] Meeting Tuesday August 5th at 19:00 UTC
Hi everyone, The OpenStack Infrastructure (Infra) team is hosting our weekly meeting on Tuesday August 5th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend. Meeting log and minutes from our meeting last week available here: Minutes: http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-29-19.01.html Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-29-19.01.txt Log: http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-29-19.01.log.html -- Elizabeth Krumbach Joseph || Lyz || pleia2 http://www.princessleia.com ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] How upstream jenkins coohses server
Hi Jeremy, I think that the question is whose CIs will be run for each patch. For example, this patchsets(1)(2) have different CIs being run in each. What is the criteria, and who selects what runs in each? 1 https://review.openstack.org/#/c/109481/ 2 https://review.openstack.org/#/c/111760/ On Mon, Aug 4, 2014 at 2:18 PM, Jeremy Stanley wrote: > On 2014-08-04 17:09:31 + (+), Wilfredo Ronsini wrote: >> For the CI Test system, I would like to know how to upstream >> jenkins chooses which Third Party CI will be used, if a ramdom >> pick or will it choose based on the driver being tested? > [...] > > The upstream CI does not choose anything there... each third-party > CI system listens to the upstream Gerrit's event stream and reacts > to new patchsets and comments. > > http://ci.openstack.org/third_party.html#reading-the-event-stream > > Hopefully that helps? > -- > Jeremy Stanley > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] How upstream jenkins coohses server
On 2014-08-04 14:54:11 -0300 (-0300), Erlon Cruz wrote: > I think that the question is whose CIs will be run for each patch. > For example, this patchsets(1)(2) have different CIs being run in > each. What is the criteria, and who selects what runs in each? [...] It's up to the individual CI operators to configure their systems to run and report on whatever they think they should. Generally the project(s) which you're testing will provide some guidelines as to what they want to see tested (so for Cinder, you should be asking the Cinder development community as they're your primary audience). -- Jeremy Stanley ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [git-review] Supporting development in local branches
Hello, git-review users! I'd like to gather feedback on a feature I want to implement that might turn out useful for you. I like using Git for development. It allows me to keep track of current development process, it remembers everything I ever did with the code (and more). I also really like using Gerrit for code review. It provides clean interfaces, forces clean histories (who needs to know that I changed one line of code in 3am on Monday?) and allows productive collaboration. What I really hate is having to throw away my (local, precious for me) history for all change requests because I need to upload a change to Gerrit. That's why I want to propose making git-review to support the workflow that will make me happy. Imagine you could do smth like this: 0. create new local branch; master: M-- \ feature: * 1. start hacking, doing small local meaningful (to you) commits; master: M-- \ feature: A-B-...-C 2. since hacking takes tremendous amount of time (you're doing a Cool Feature (tm), nothing less) you need to update some code from master, so you're just merging master in to your branch (i.e. using Git as you'd use it normally); master: M---N-O-... \\\ feature: A-B-...-C-D-... 3. and now you get the first version that deserves to be seen by community, so you run 'git review', it asks you for desired commit message, and all changes from your branch is uploaded to Gerrit as _one_ change request; master: M---N-O-... \\\E* <= uploaded feature: A-B-...-C-D-...-E 4. you repeat steps 1 and 2 as much as you like; 5. and all consecutive calls to 'git review' will show you last commit message you used for upload and use it to upload new state of your local branch to Gerrit, as one change request. Note that during this process git-review will never run rebase or merge operations. All such operations are done by user in local branch instead. Now, to the dirty implementations details. - Since suggested feature changes default behavior of git-review, it'll have to be explicitly turned on in config (review.shadow_branches? review.local_branches?). It should also be implicitly disabled on master branch (or whatever is in .gitreview config). - Last uploaded commit for branch will be kept in refs/review-branches/. - For every call of 'git review' it will find latest commit in gerrit/master (or remote and branch from .gitreview), create a new one that will have that commit as its parent and a tree of current commit from local branch as its tree. - While creating new commit, it'll open an editor to fix commit message for that new commit taking it's initial contents from refs/review-branches/ if it exists. - Creating this new commit might involve generating a temporary bare repo (maybe even with shared objects dir) to prevent changes to current index and HEAD while using bare 'git commit' to do most of the work instead of loads of plumbing commands. Note that such approach won't work for uploading multiple change request without some complex tweaks, but I imagine later we can improve it and support uploading several interdependent change requests from several local branches. We can resolve dependencies between them by tracking latest merges (if branch myfeature-a has been merged to myfeature-b then change request from myfeature-b will depend on change request from myfeature-a): master:M---N-O-... \\\-E* myfeature-a: A-B-...-C-D-...-E \ \ \ J* <= uploaded myfeature-b: F-...-G-I-J This improvement would be implemented later if needed. I hope such feature seams to be useful not just for me and I'm looking forward to some comments on it. -- Kind regards, Yuriy. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
