Last modified: 2014-10-06 09:52:16 UTC
Causes various false positives and hilarious failures about missing files and what not.
https://gerrit.wikimedia.org/r/#/c/71103/
Use the web interface ? :-)
On changes such https://gerrit.wikimedia.org/r/#/c/117146/ we always get a down vote because Jenkins tries to build it.
(In reply to Antoine "hashar" Musso from comment #3) > Use the web interface ? :-) That is not an option because for change I'm making most often (disabling Verified/Submit for regular users) doesn't work in the the web interface. The web interface of Gerrit is broken. It requires all values to be autocompleted, and one due to a bug in Gerrit you can only autocomplete group names you're an admin of (so only Gerrit root admins can make changes that introduce group names). Through the commit interface it works fine however, and there is no security reason to restrict it either, it's purely a bug in the UI. Either way, there are other branches as well. Zuul should only run on repository code related branches. These meta branches, unless we plan to write jobs for them (at which point we should have to explicitly whitelist them), there is no point in letting Zuul run over it.
I was merely minding Timo sorry ;-D You can potentially add a ref filter on each of the Zuul pipeline. Something like: - name: test trigger: gerrit: - event: patchset-created ref: ^(?!refs/meta/config).*$ That should discard patches on refs/meta/config
*** Bug 64678 has been marked as a duplicate of this bug. ***
