[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36591#comment-36591 ]
Hmm… I think we fixed this in V2 – its a bit tricky to get a proper fox for this in V1, might even be impossible.
CQ failed due to a patch from a non-whitelisted email
Key: OVIRT-2035 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Evgheni Dereveanchin Assignee: infraWhile investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: Failed CQ job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleFull 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building Related build-artifacts job: http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-fc27-x86_64/32/console 07:07:10 shell-scripts/whitelist-filter.sh 07:07:10 USER bburmest@redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING 07:07:10 Build step ‘Execute shell’ marked build as failure Merged gerrit patch: https://gerrit.ovirt.org/#/c/91277/
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)