[
https://ovirt-jira.atlassian.net/browse/OVIRT-1701?page=com.atlassian.jir...
]
eyal edri commented on OVIRT-1701:
----------------------------------
It might not be a bug, but still confusing error message which isn't relevant to the
job.
I think we should at least check the option to change the error printed to the screen to
skip it for jobs which are not using find bugs.
If it's not possible with current tooling, we should consider this as an improvement
when we move check-patch to use the pipeline flow.
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: infra
Example_
http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/...
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)