[
https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] updated OVIRT-1174:
---------------------------------------------
Resolution: Won't Fix
Status: Done (was: To Do)
I think that as long as we don't have valid projects that doesn't produce
artifacts we shouldn't fix it.
As for containers - we will probably not trigger 'deploy-to-experimental' job
anyway and use a different flow.
> 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.824.3#100035)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
