[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs

[eyal edri [Administrator] (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27602#comment-27602 ] 

eyal edri [Administrator] commented on OVIRT-1174:
--------------------------------------------------

Its true that we need to handle that, but don't we want to know on a project that doesn't produce artifacts?
otherwise that'st the point of running build-artifacts? 

We do need to support other types like ISO and image files, but I wonder if we should keep failing if no artifacts are found.

[~rgolan] any reason vdsmfake doesn't build anything in the build-artifacts job?

> deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: OVIRT-1174
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174
>             Project: oVirt - virtualization made easy
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Barak Korren
>            Assignee: infra
>
> deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it.
> To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it.
> Here is an example run of deploy-to-experimental that failed because of this:
> http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/



--
This message was sent by Atlassian JIRA
(v1000.773.3#100032)