[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jir... ] Barak Korren edited comment on OVIRT-1408 at 5/25/17 2:50 PM: -------------------------------------------------------------- {quote} The build-artifacts had to be failing for a couple of last weeks, no complain received. {quote} Did you try to ask the CI team for help? {quote} The project is built externally (copr) and rpms are pulled semi-automatically (project releng-tools, Sandro). {quote} releng-tools just pulls into official repos, and hopefully we'll retire that way of doing things soon. Among other things it means the package does not make in into the nightly releases. {quote} Is CI really involved? If so, what is the minimum of automation/ to remain? {quote} Not sure I get the 1st part of the question. At bare minimum to get stuff into the 'experimental' flow that runs OST and delivers to 'tested' and the nightly snapshot, you need a build_artifacts job. It doesn't really has to do the building, but it needs to leave RPMs in 'exported-artifacts' when it is done. was (Author: bkorren(a)redhat.com): {quote} The build-artifacts had to be failing for a couple of last weeks, no complain received. {quote} Did you try to ask the CI team for help? {quote} The project is built externally (copr) and rpms are pulled semi-automatically (project releng-tools, Sandro). {quote} releng-tools just pulls into official repos, and hopefully we'll retire that way of doing things soon. Amount other things it means the package does not make in into the nightly releases. {quote} Is CI really involved? If so, what is the minimum of automation/ to remain? {quote} Not sure I get the 1st part of the question. At bare minumun to get stuff into the 'experimental' flow that runs OST and delivers to 'tested' and the nightly snapshot, you need a build_artifacts job. It doesn't really has to do the building, but it need to leave RPMs in 'exported-artifacts' when it is done. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)