Re: [OpenStack-Infra] How upstream jenkins coohses server

2014-08-04 Thread Jeremy Stanley
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 opera

Re: [OpenStack-Infra] How upstream jenkins coohses server

2014-08-04 Thread Erlon Cruz
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

Re: [OpenStack-Infra] How upstream jenkins coohses server

2014-08-04 Thread Jeremy Stanley
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 th

[OpenStack-Infra] How upstream jenkins coohses server

2014-08-04 Thread Wilfredo Ronsini
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 informati