[
https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-1408:
-------------------------------------
{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.
Please remove github/ovirt-web-ui from standard CI
--------------------------------------------------
Key: OVIRT-1408
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1408
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: Marek Libra
Assignee: infra
Please remove github/ovirt-web-ui from standard CI since Travis is used instead.
--
This message was sent by Atlassian JIRA
(v1000.1010.0#100044)