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

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-1174:
-------------------------------------

Reopening, I don't think limiting what people can do with build-artifacts is a good idea. Its called "build-artifacts" ant not "build RPMS for OST" and people should be free to use it to build any artefacts they need. And it shouldn't choke out infra if someone is not building RPMs (We may not test and release non-RPM artifacts, but we certainly should not prevent them from being built).

> 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
>             Fix For: OVIRT-INFRA-MAR-2017
>
>
> 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.910.0#100040)