Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs

Description

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/

Activity

Show:

Barak Korren June 24, 2018 at 8:35 AM

We no longer use deploy-to-experimental anywhere.

Barak Korren April 25, 2017 at 7:16 AM

Linking to a suggested repoman fix () that would solve this.

Barak Korren April 25, 2017 at 7:15 AM

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).

Eyal Edri March 20, 2017 at 2:45 PM

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.

Eyal Edri February 22, 2017 at 9:45 AM

I know, this is why I wrote:
"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."

Won't Fix

Details

Assignee

Reporter

Components

Priority

Created February 21, 2017 at 3:27 PM
Updated June 24, 2018 at 8:35 AM
Resolved March 20, 2017 at 2:45 PM