[ https://ovirt-jira.atlassian.net/browse/OVIRT-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35144#comment-35144 ]
[~eedri] That is what it does now. It checks if there is a directory called ‘find-bugs’ and if so – it collects the XMLs and parse them. The message you see in the job is from the publisher. Unfortunately, it's not supported to set find-bugs as a conditional publisher with the current version of JJB. We'll have to wait for JJB 2 which is currently in its beta state to be released.
jenkins jobs try to collect find-bugs data even on non engine jobs
Key: OVIRT-1701 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1701 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infraExample_ http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/console Shows the failure: 09:44:19 Archiving artifacts*09:44:19* Recording test results*09:44:20* [ovirt-wgt_master_check-patch-fc26-x86_64] $ /bin/bash -xe /tmp/CommandInterpreterCondition8048067474184520875.sh*09:44:20* + find exported-artifacts/find-bugs/ -name ‘*.xml'*09:44:20* + grep -e '.*'*09:44:20* find: 'exported-artifacts/find-bugs/’: No such file or directory*09:44:20* Run condition [Execute Shell] preventing perform for step [[Publish FindBugs analysis results]] Jobs shouldn't try to collect something which is not supposed to exist. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100065)