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 <fungi at yuggoth.org> wrote: > On 2014-08-04 17:09:31 +0000 (+0000), 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 at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra