[
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira...
]
Barak Korren edited comment on OVIRT-904 at 12/8/16 10:36 AM:
--------------------------------------------------------------
[~gshereme(a)redhat.com] are you doing that manually, or do you have some automation built
around it?
I'm not sure oVirt's own infra would be the best place, because Patternfly is not
strictly an oVirt project.
Perhaps make travis run the build in Copr, and then take the result and push it to
GitHub's artifact storage?
Another possibility is to use [
BinTray|https://bintray.com/]
We might eventually mirror this in oVirt infra to make CI resilient to changes there (see
OVIRT-575)
was (Author: bkorren(a)redhat.com):
[~gshereme(a)redhat.com] are you dong that manually, or do you have some automation built
around it?
I'm not sure oVirt's own infra would be the best place, because Patternfly is not
strictly an oVirt project.
Perhaps make travis run the build in Copr, and then take the result and push it to
GitHub's artifact storage?
Another possibility is to use [
BinTray|https://bintray.com/]
We might eventually mirror this in oVirt infra to make CI resilient to changes there (see
OVIRT-575)
False CI-1 due to unreachable
copr-be.cloud.fedoraproject.org
-------------------------------------------------------------
Key: OVIRT-904
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-904
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: danken
Assignee: infra
Many patches on
https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
failure: repodata/repomd.xml from patternfly: [Errno 256] No more
mirrors to try.
http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epe...:
[Errno 14] curl#7 - "Failed connect to
copr-be.cloud.fedoraproject.org:80; No route to host"
http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epe...
--
This message was sent by Atlassian JIRA
(v1000.620.0#100023)