Open Stack

Hi Jeremy:

I have disabled the 2 jobs which were reporting "SKIPPED" results on our Zuul/Jenkins server. I'll be working with the teams who own the corresponding testbeds to resolve the merge conflicts which are preventing them from testing patchsets outside of their own (unmerged) plugin patchsets.

As for having multiple review comments per patchset being reviewed, the best that I can do in the near term is to post 2 comments per patchset review, since we have some of our CI testbeds which are in a DMZ, and some that are inside a corporate firewall, so 2 separate Zuul/Jenkins servers are required.

I brought up this issue re. multiple review comments during the OpenStack 3rd Party IRC meeting on Monday. Some historical background: When I originally requested multiple CI accounts for our various Neutron plugins, I was told (by Clark) that each company was only allowed one CI account (presumably so that there would be one point of contact within the community, and the chronological list of review comments for each patchset would not be unnecessarily be overrun with comments from one company). As I explained in Monday's IRC meeting, supporting 6 different test setups under one account (with 2 more coming in the K release cycle) has become unmanageable for us. This also presents problems going forward when we try to obtain voting rights, since all of our test setups under our one account would have to show and maintain stability before earning voting rights (i.e. it's all or none). The restriction that we only provide one review comment per patchset is also cumbersome for a few reasons:
* Queue backups on slower test setups effect the test result latency for other setups.
* Before a plugin's initial patchset is approved and merged, we would like to give higher priority test access to that plugin's code reviews. Zuul supports high priority pipelines, but the Jenkins jobs need to be sending review comments directly to Gerrit in order to implement this per-patchset priority scheme.

On Monday's IRC, I was told that we would be allowed to split off our testbeds into their own separate CI accounts (so that managing/maintaining can be scaled appropriately), and we're in the process of doing this, but it will take some time to re-configure our Zuul/Jenkins and request the accounts.

In the meantime, we are configured to send 2 comments per patchset review, one from our DMZ Zuul/Jenkins setup, and one for our CI setup that is behind a corporate firewall.

If this is acceptable, can you please re-enable our Gerrit CI account?

Thank you,
Dane

-----Original Message-----
From: Jeremy Stanley [mailto:fungi at yuggoth.org] 
Sent: Thursday, September 11, 2014 10:29 AM
To: cisco-openstack-neutron-ci(mailer list); Dane Leblanc (leblancd); Nikolay Fedotov (nfedotov)
Cc: Announcements for third party CI operators.
Subject: Cisco CI account is temporarily disabled in Gerrit

Looking at https://review.openstack.org/120730 as an example (click the Toggle CI button at the bottom to see comment details), the Cisco CI account 10192 is adding multiple comments on one patchset.
It appears to separate out notices of skipped jobs into additional comments, which it definitely should not do.

I was unable to raise Dane in IRC, and so have temporarily disabled the account to prevent further disruption. Please correct this and let the project infrastructure team know in IRC (#openstack-infra on
Freenode) once ready for it to be reenabled. Thanks!
--
Jeremy Stanley