Hi, I'm investigating on a failure[2 <http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-el7-x86_64/1/console>] on jenkins jobs for ovirt-engine-api-model[1 <http://jenkins.ovirt.org/search/?q=ovirt-engine-api-model_master_build-artifacts>] on el7. Before I further invest time on it, I'd like to understand the purpose of the job.
As far as I can tell the project is building some documentation in different formats and a tarball with the sources: asciidoctor.css 28.92 KB model.adoc 1.24 MB model.csv 264.77 KB model.html 3.37 MB model.json 7.39 MB model.xml 6.09 MB ovirt-engine-api-model-4.3.8.20180213gita1f6d9a.tar.gz 246.48 KB I think that some way the output may be used by http://ovirt.github.io/ovirt-engine-api-model/ but I don't feel like this is really done. I also see that artifacts are published on https://search.maven.org/#artifactdetails%7Corg.ovirt.engine.api%7Cmodel%7C4.3.7.color%7Cjar <https://search.maven.org/#artifactdetails%7Corg.ovirt.engine.api%7Cmodel%7C4.3.7.color%7Cjar> but this is also not done by the jenkins jobs. I see this artifacts is required in ovirt-engine pom.xml: <model.version>4.3.7</model.version> So I would expect the job to prepare a rpm including this jar and pom to be required in ovirt-engine spec file, at least if we follow Fedora packaging guidelines. As is, this jobs seams meaningless. What should we do here? Drop the job? Fix it for building rpms? [1] http://jenkins.ovirt.org/search/?q=ovirt-engine-api-model_master_build-artifacts [2] http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-el7-x86_64/1/console -- 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>
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel